Skip to main content
Glama

mcp-server

by io.github.localgov-jp

find_practitioner

Read-onlyIdempotent

Recommend 3 Japanese licensed practitioner types (行政書士 / 税理士 / 中小企業診断士 / 社労士) for the grant's category. Returns role explanations and official-association registry links. Informational only — LocalGov.jp does NOT broker, refer, or accept commission for these recommendations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grant_idYesSubsidy id (the recommendation is shaped by the grant's category and amount tier)
industry_hintNoFree-text industry context, e.g. "飲食業", "製造業"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noticeYes
grant_idYes
practitionersYes
legal_disclaimerYes

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description aligns with annotations (readOnlyHint, idempotentHint) and adds that it is informational only, returning explanations and links without brokering. No hidden behaviors or contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: first defines function and output, second states limitation. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description sufficiently explains what the tool returns (role explanations and registry links) and the informational nature. Complete for the tool's purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. The description adds value beyond the schema by explaining that grant_id shapes the recommendation based on category and amount tier. Industry_hint is simply restated from the schema, so marginal additional meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that it recommends 3 Japanese licensed practitioner types based on the grant's category. The verb 'recommend' and resource 'practitioner types' are specific. The tool is distinct from siblings that focus on subsidies, grants, or receipts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: it is used for grant categories and is informational only. It does not explicitly state alternatives or when not to use, but the context is sufficient for an agent to infer appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: comparing subsidies across municipalities, recommending practitioners, finding supplementary grants, listing grants for a municipality, getting subsidy details, searching subsidies, subscribing to changes, and verifying receipts. There is no overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., compare_municipal_subsidies, find_practitioner, search_subsidies). No deviations or mixed conventions.

Tool Count5/5

With 8 tools, the set is well-scoped for a server focused on Japanese subsidies. Each tool serves a distinct function without being excessive or insufficient.

Completeness5/5

The tool set covers the full lifecycle for subsidy data: search, get details, list by municipality, compare across municipalities, find supplementary grants, practitioner recommendations, subscription for changes, and receipt verification. No obvious gaps for the intended domain.

Resources