Skip to main content
Glama
Sign In

Japan Public Data (法人番号・登録支援機関・官公需入札)

by io.github.takaratomita
OverviewDiscussionsAdmin

Search Japanese public procurement notices

search_local_govt_bids
Read-onlyIdempotent

Search bid and tender notices from Japanese local governments and national agencies via the KKJ (官公需情報ポータルサイト) search API by the Small and Medium Enterprise Agency. Filter by keywords (AND), prefecture, issuing organization and notice date. Returns title, organization, dates and the notice URL. 官公需情報ポータルサイトの検索APIで、自治体・国の機関の入札・公募情報をキーワード・都道府県・機関名・公告日で検索します。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_local_govt_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 20) / 最大件数
queryNoKeywords separated by spaces (AND) / キーワード（空白区切りでAND）
sinceNoNotices issued on or after this date, YYYY-MM-DD (default: 30 days ago) / 公告日がこの日以降（既定：30日前）
prefectureNoPrefecture name / 都道府県（例：東京都、大阪）
organizationNoIssuing organization, partial match / 機関名（部分一致。例：横浜市）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety and external-query profile. The description adds useful context about the source API and the fields returned, but it does not mention authentication, rate limits, or pagination behavior.

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?

The description is front-loaded with the purpose, filters, and return values in a compact form. The bilingual repetition is useful for a Japanese-language tool but does duplicate content, keeping it slightly short of maximally concise.

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 search tool with full schema coverage and strong annotations, the description supplies the key remaining context: the external source, filtering capabilities, and returned fields. No output schema exists, but the description names the return values sufficiently.

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%, so all five parameters are already documented in the input schema. The description reinforces the keyword AND behavior and the filterable fields, but it adds little beyond what the schema provides and does not explain the limit parameter.

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 states a specific verb and resource: searching bid and tender notices from Japanese local governments and national agencies via the KKJ API. It also names the filters and return fields, so an agent can distinguish this from the unrelated sibling tools.

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?

The description makes the search use case clear through its scope and filters, but it does not explicitly state when to use this tool versus alternatives or when not to use it. The sibling tools are unrelated, so the implied usage is adequate but not fully guided.

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

All Japan Public Data (法人番号・登録支援機関・官公需入札) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources