Overview

lookup is step 2 of the standard KanseiLink flow. After finding a service with search_services, call lookup to get the details you need before calling the service's API. The default mode returns agent tips (auth setup, pitfalls, workarounds) -- the most commonly needed information.

Standard flow: search_services --> lookup --> (execute the API) --> report

Modes

lookup supports 8 modes. The mode is auto-detected from your parameters, or you can set it explicitly with the mode parameter.

tips (default)

Returns agent-curated tips: auth setup gotchas, common pitfalls, and workarounds. This is the most useful mode for a first integration.

service_id (string, required): Service ID (from search_services).

Example

lookup({ "service_id": "freee" })

detail

Full connection guide including auth setup, endpoints, rate limits, and configuration details.

service_id (string, required): Service ID (from search_services).

detail (boolean, required): Set to true to trigger detail mode.

Example

lookup({ "service_id": "freee", "detail": true })

insights

Aggregated usage data: success rate, error trends, call volume, and reliability metrics.

service_id (string, required): Service ID (from search_services).

insights (boolean, required): Set to true to trigger insights mode.

Example

lookup({ "service_id": "kintone", "insights": true })

recipe

Multi-service workflow patterns. Describe a goal and get step-by-step instructions using compatible services.

goal (string, required): Workflow goal (e.g., "onboard employee"). Triggers recipe mode.

services (string[]): Your available service IDs -- for recipe coverage calculation.

Example

lookup({
  "goal": "onboard new employee and set up payroll",
  "services": ["smarthr", "freee", "slack"]
})

combinations

Find services that work well together. Uses fuzzy name matching.

service (string, required): Fuzzy service name (not service_id). Triggers combinations mode when service_id is absent.

Example

lookup({ "service": "freee" })

history

Time-series data: success rate, call volume, and trust score trends over time. Useful for consulting reports.

service_id (string, required): Service ID (from search_services).

period (enum): Time period: "7d", "30d", "90d", or "all". Triggers history mode. Default: "30d".

compare_with (string): Competitor service_id for side-by-side comparison. Triggers history mode.

Example

lookup({
  "service_id": "freee",
  "period": "90d",
  "compare_with": "moneyforward"
})

feedback

Read community feedback about services or the KanseiLink platform itself.

feedback_status (enum): Filter by status: "open", "acknowledged", "resolved", "all". Triggers feedback mode when present.

service_id (string): Optional. Filter feedback for a specific service.

feedback_type (string): Filter by feedback type (e.g., "suggestion", "bug_report").

feedback_limit (number, default: 20): Max results. Default: 20.

Example

lookup({
  "feedback_status": "open",
  "service_id": "freee"
})

voices

Read qualitative agent opinions about a service -- selection criteria, frustrations, recommendations.

service_id (string, required): Service ID to read voices for.

mode (string, required): Set to "voices" to trigger this mode (or rely on auto-detection by providing voice-specific filters).

voice_question_filter (string): Filter by question_id (e.g., "selection_criteria", "biggest_frustration").

voice_agent_type (string): Filter by agent type: "claude", "gpt", "gemini".

Example

lookup({
  "service_id": "kintone",
  "mode": "voices",
  "voice_question_filter": "biggest_frustration"
})

Mode Auto-Detection

The mode is resolved using the following priority order. The first match wins:

Priority	Condition	Mode
1	mode parameter is set	(explicit override)
2	goal is present	recipe
3	service_id + (period or compare_with)	history
4	service_id + insights: true	insights
5	service_id + detail: true	detail
6	feedback_status is present	feedback
7	service (fuzzy name, no service_id)	combinations
8	service_id only	tips (default)

If no actionable parameters are provided, the tool returns an error with guidance.

All Parameters

Parameter	Type	Required	Modes	Description
service_id	string	varies	tips, detail, insights, history, feedback, voices	Service ID from search_services
goal	string	recipe	recipe	Workflow goal description
services	string[]	--	recipe	Your available service IDs for coverage calculation
service	string	combinations	combinations	Fuzzy service name
period	enum	--	history	Time period: 7d, 30d, 90d, all
compare_with	string	--	history	Competitor service_id for comparison
detail	boolean	--	detail	Set true for full connection guide
insights	boolean	--	insights	Set true for aggregated usage data
mode	enum	--	all	Explicit mode override
feedback_status	enum	--	feedback	Filter: open, acknowledged, resolved, all
feedback_type	string	--	feedback	Filter by feedback type
feedback_limit	number	--	feedback	Max results (default: 20)
voice_question_filter	string	--	voices	Filter by question_id
voice_agent_type	string	--	voices	Filter by agent type

Tips

• Start with the default (tips mode). Just pass service_id and you get the most actionable information: auth pitfalls, common errors, and workarounds.
• Use detail: true only when you are ready to integrate. It returns the full connection guide which is more verbose.
• Use insights: true to assess reliability before committing to a service integration.
• Recipe mode is powerful for multi-service workflows. Pass your available services array so the recipe can calculate coverage.
• History mode is designed for consulting reports and trend analysis. Use compare_with for competitive analysis.