Skip to main content
Glama

get_subsidy_detail

Read-onlyIdempotent

Retrieve a subsidy's details—rate, eligibility, regions, application periods, guidelines, and deadline—using an ID from search results.

Instructions

補助金1件の詳細を取得する。

補助率、利用目的、対象業種、公募要領の本文(HTMLをプレーンテキスト化
したもの)、募集の回(workflow)ごとの対象地域と受付期間、事業終了
期限が返る。添付ファイル(公募要領・申請様式)は本体(Base64)を
省略し、ファイル名などのメタデータだけを返す。日時はUTC。

Args:
    subsidy_id: search_subsidies が返した補助金ID(18文字以下)。
    version: 詳細APIの版。v2 は募集の回ごとに地域と期間を持つ形で、
        既定はこちら。v1 は地域と期間が公募直下にある旧形式で、
        workflow 1件に正規化して返す。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subsidy_id": "<subsidy_id>"
    },
    "name": "get_subsidy_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNov2
subsidy_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavioral context beyond that: attachments are returned with metadata only and the Base64 body omitted, and all datetimes are UTC — details an agent could not infer from the annotations. The enumeration of returned fields overlaps somewhat with the existing output schema, which keeps it just short of a 5.

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

Conciseness4/5

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

Purpose is front-loaded and the Args block is well organized, with no filler. The return-value sentence is dense and partially redundant with the output schema, which is the only real efficiency cost.

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?

For a read-only two-parameter detail tool with an output schema and full annotation coverage, nothing an agent needs to call it correctly is missing: ID provenance, version semantics, datetimes timezone, and attachment handling are all stated.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and it does: subsidy_id is defined by provenance and length, and version is explained in terms of the actual response shape difference (per-workflow region/period vs. legacy flat region/period normalized to one workflow). This meaningfully extends the bare v1/v2 enum.

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 first sentence states a specific verb and resource ('補助金1件の詳細を取得する'), and the args section ties the input to 'search_subsidies が返した補助金ID', making the search-then-detail relationship explicit. An agent can distinguish this from the sibling without opening either schema.

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 dependency on search_subsidies output makes the usage sequence clear, and the version argument is given explicit guidance (v2 is the default per-workflow shape; v1 is the legacy shape normalized to a single workflow). There is no explicit when-not-to-use statement, but the workflow context is unambiguous.

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

Deploy Server

Other Tools