Skip to main content
Glama

search_subsidies

Read-onlyIdempotent

Search Japanese government subsidies registered with J-Grants by keyword and filter by acceptance status, industry, purpose, employee count, or region to identify relevant funding programs.

Instructions

JGrantsに登録された補助金をキーワードで検索する。

返るのは制度の情報(補助金名・対象地域・従業員数の条件・補助上限額・
受付期間)で、申請者や採択企業の情報は含まれない。キーワード検索の
絞り込みは粗く、無関係な公募が混ざることがある。受付期間の日時は
UTC(APIの返却値そのまま)。

Args:
    keyword: 検索キーワード(2文字以上255文字以下、必須)。
    sort: 並べ替え項目。created_date / acceptance_start_datetime /
        acceptance_end_datetime。
    order: ASC(昇順)または DESC(降順)。
    acceptance: 1 は受付中のみ、0 は受付前・終了分も含む全て。
    industry: 業種での絞り込み(APIの定義値)。
    use_purpose: 利用目的での絞り込み(APIの定義値)。
    target_number_of_employees: 従業員数の条件(APIの定義値)。
    target_area_search: 補助対象地域での絞り込み(例: 東京都)。

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

NameRequiredDescriptionDefault
sortNoacceptance_end_datetime
orderNoASC
keywordYes
industryNo
acceptanceNo
use_purposeNo
target_area_searchNo
target_number_of_employeesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 the safety profile is covered. The description adds genuinely new behavioral context: results are institution records only, keyword matching is loose and may include irrelevant entries, and acceptance-period timestamps are UTC as returned by the API. It does not mention result limits or pagination.

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?

Front-loads purpose and return scope, then lists arguments compactly; every sentence carries information. Minor waste in restating the keyword length bounds already enforced by the schema.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not strictly required, and the description still usefully characterizes the payload. However, for an eight-parameter search tool with zero schema description coverage, the vague 'API definition values' for three filter parameters and the absence of any result-count or pagination note leave real gaps.

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 0%, so the description must carry parameter meaning, and it does document all eight. It adds real meaning for acceptance (1 = currently open, 0 = includes upcoming and closed) and target_area_search (example: 東京都), but industry, use_purpose and target_number_of_employees are only described as 'API definition values', leaving the agent without valid values for three filters.

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?

States a specific verb and resource (search JGrants-registered subsidies by keyword) and defines the returned scope precisely: institution-level data only, excluding applicant/adopted-company information. It does not name the sibling get_subsidy_detail, so the search-vs-detail distinction is only implied by the scope sentence.

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 by the verb and by the caveat that keyword filtering is coarse and may return unrelated listings, which tells the agent to expect noise. There is no explicit statement of when to use this versus get_subsidy_detail, nor any prerequisite or follow-up guidance.

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