Skip to main content
Glama
Sign In
jgrants-util-mcp-server

jgrants-util-mcp-server

by gotoai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_subsidy_detail

Read-only

Retrieve a Japanese government subsidy's details—overview, eligibility, rates, amounts, dates, portal URL, and attachment list—by subsidy ID to support application research.

Instructions

Get one subsidy's full details: overview, eligibility, subsidy rate, amounts, dates, portal_url, and a list of its attachments (read them with read_attachment).

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
subsidy_idYesThe id from search_subsidies.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description need not repeat safety properties. It adds useful behavioral context by naming the returned fields and pointing to read_attachment for attachment contents.

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?

A single, front-loaded sentence with no wasted wording. It efficiently packs the resource, returned fields, and attachment-routing guidance.

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 one-parameter detail-fetch tool with an output schema and read-only annotations, the description is complete. It tells the agent what the tool returns and how to proceed with attachments.

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

Parameters3/5

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

Schema description coverage is 100%, and the parameter is already documented as 'The id from search_subsidies.' The description adds no further meaning about subsidy_id formatting or constraints, so this is the expected baseline.

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 uses a specific verb and resource: 'Get one subsidy's full details.' It enumerates the returned content and distinguishes this detail tool from sibling tools like search_subsidies and read_attachment.

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?

It clearly positions read_attachment as the alternative for attachment contents, which is useful routing guidance. It does not explicitly state when to use search_subsidies first, though the subsidy_id parameter description implies that workflow.

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