jgrants-util-mcp-server

Overview Schema Source Related Servers Discussions Admin

search_subsidies

Read-only

Find Jグランツ subsidies by keyword, industry, purpose, area, and employee count; get paginated summaries with IDs and portal links for application follow-up.

Instructions

Search Jグランツ subsidies by keyword and filters. Returns one page of summaries with each subsidy's id and portal_url; total_count and next_offset tell whether more pages exist.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_subsidies"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No		acceptance_end_datetime
`limit`	No
`order`	No		ASC
`offset`	No
`keyword`	Yes	One search term, 2–255 characters, no spaces.
`industry`	No	Industries, any of.
`acceptance`	No	Only subsidies open for applications now.
`use_purpose`	No	Purposes, any of.
`target_area_search`	No	Target area.
`target_number_of_employees`	No	Employee-count bracket.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely useful behavior beyond them: results are paged, and total_count/next_offset signal whether more pages exist. It stops short of describing ordering of results or rate limits, keeping it out of the top band.

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 sentences, zero filler, with the purpose front-loaded and the pagination model stated immediately after. Every clause earns its place.

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

Completeness4/5

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

With 10 parameters, an output schema, and annotations present, the description covers purpose, result granularity, and pagination — enough to call the tool correctly. The remaining gap is that it never notes the follow-up detail tool or the single-term restriction on keyword.

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 60%, so the schema documents the most important parameters (keyword constraints, industry, use_purpose, area). The description only refers generically to 'keyword and filters' and adds no meaning about how filters combine or how sort/order interact with offset.

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

Purpose4/5

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

The description gives a specific verb and resource ('Search Jグランツ subsidies by keyword and filters') and states the return shape (one page of summaries with id and portal_url). It is clearly distinguishable from get_subsidy_detail and load_guideline, though it doesn't explicitly name them as follow-ups.

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

Usage Guidelines3/5

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

Usage is implied: this is the paginated discovery step whose results carry an id for a later detail lookup. However, there is no explicit when-to-use or when-not-to-use guidance, and no routing statement toward get_subsidy_detail or load_guideline.

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

Deploy Server