Skip to main content
Glama

入札案件観測所

名前から発注機関・企業を探す

resolve_names
Read-onlyIdempotent

Find buyers or suppliers by partial name, abbreviation or former name (e.g. 国交省, NTT, 旧 防衛庁) and get their IDs. Only for when the user wants to look up or list names, or when another tool returned candidates; the buyer and supplier arguments of the other tools already accept names and abbreviations such as 国交省, so do not call this first. 発注機関・企業の名前の検索

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": {
      "query": "<query>"
    },
    "name": "resolve_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoPrefecture. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
kindNobuyer = procuring entities, supplier = companies, any (default) = both
limitNo1-10 (default 10)
queryYesPart of a name, an abbreviation, or a 13-digit corporate number

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
totalYes
accessNoWhether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login_required / plan_required = the item exists but is available only under other access conditions of the site (sign-in, or a plan)
sourceYes
cite_asNoOne-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
messageNo
relatedNoFacts related to this result (counts) and the tool call that returns them
retrievedYes
candidatesYes
data_as_ofYes
restrictedNoItems that exist but are not returned here, with their access value. An item listed here is not missing from the data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description adds the non-obvious workflow fact that this tool is usually redundant because other tools accept names inline. It does not cover result volume or fallback behavior for zero matches, but with an output schema present that gap is minor.

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 guidance is front-loaded and the key routing warning comes before any elaboration. The trailing Japanese phrase "発注機関・企業の名前の検索" merely restates the title and could be dropped, keeping it from a 5.

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?

Given an output schema, full parameter descriptions and rich annotations, the description covers what an agent needs to decide whether to call this at all — the main risk with a lookup tool. Only edge-case behavior (empty results, disambiguation among multiple matches) is left implicit.

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 the baseline is 3. The description adds only a little beyond it — notably that former names can be matched, which the `query` schema field does not mention — but says nothing about `area`, `kind` or `limit` beyond what the schema already documents.

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?

Uses a specific verb and resource ("Find buyers or suppliers by partial name, abbreviation or former name") and states the outcome ("get their IDs"), with concrete examples (国交省, NTT, 旧 防衛庁) that make the lookup semantics unambiguous.

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

Usage Guidelines5/5

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

Explicitly restricts use to two situations (user wants to look up/list names, or another tool returned candidates) and explicitly warns against calling it first because sibling tools' buyer/supplier arguments already accept names and abbreviations. Both the when and the when-not are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources