Skip to main content
Glama

入札案件観測所

発注機関の要約

get_buyer_profile
Read-onlyIdempotent

Summary of one procuring entity in Japan (ministry, agency, prefecture, city, public corporation): award counts by year and category, most frequent suppliers, and its currently open notices. If the name matches several entities, candidates are returned instead of a guess. When records exist only per department (e.g. 岡崎市 総務部契約課), a city or prefecture name returns the departments combined (departments). 発注機関・官公庁・自治体

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": {
      "buyer": "<buyer>"
    },
    "name": "get_buyer_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoPrefecture, to tell same-name entities apart. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
buyerYesName (e.g. 福岡市, 国交省) or buyer_id
response_formatNoconcise (default): fewer fields per row. detailed: adds IDs, method, original URL and retrieval date per row.

Output Schema

NameRequiredDescriptionDefault
urlYes
areaNo
nameNo
noteYes
foundYes
levelNo
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
buyer_idNo
ambiguousNo
retrievedYes
candidatesNo
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.
awards_totalNo
open_noticesNo
top_suppliersNo
awards_by_yearNo
awards_by_categoryNo
open_notices_totalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / open_notices / items / properties / changes
      Added value: +{
      +  "description": "With changed_since: what happened to this notice on or after that date (new, or which field changed with before/after)",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "day": {
      +        "type": "string"
      +      },
      +      "field": {
      +        "type": "string"
      +      },
      +      "kind": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "day",
      +      "kind"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond annotations such as readOnly, idempotent, and openWorld=false, the description discloses two non-obvious behaviors: ambiguous names return candidates rather than a guess (no silent wrong match), and per-department records get rolled up into a `departments` field for a city or prefecture query. Those are exactly the surprises an agent needs to plan around. It does not cover rate limits or error conditions, but the annotations already carry the safety profile.

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?

Three sentences, each earning its place: the first defines the return contents, the second states the ambiguity behavior, and the third is a parenthetical example for department aggregation. The summary-of-contents comes first, which is the right priority for an agent deciding whether to call.

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 an output schema present, the description need not document the return values, and its behavioral notes cover the main ambiguity risk of a name-based lookup. The most notable remaining gap is that it does not name the sibling a caller should use to get supplier- or notice-level detail instead. Coverage is more than adequate for a 3-parameter read tool.

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

Parameters4/5

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

Schema coverage is 100%, so a baseline of 3 would apply, but the description adds meaning: the `buyer` parameter accepts an entity name and triggers the candidate-list fallback when the name is ambiguous, and a city or prefecture name aggregates department-level records. That clarifies argument behavior the schema does not spell out. The `area` and `response_format` parameters are left entirely to the schema, so this is not a 5.

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 names a specific verb and resource: a summary of one procuring entity in Japan, explicitly listing the entity types (ministry, agency, prefecture, city, public corporation) and what the summary contains (award counts by year and category, top suppliers, open notices). This distinguishes the tool from get_supplier_profile by focusing on the buying side. It declines to name an alternative tool explicitly, which is why it does not earn a 5.

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 rather than stated: you call it when you want an overview of one buyer, and the department-aggregation note tells you to pass a city or prefecture name when records are split by department. There is no explicit "when not to use this" and no routing to siblings such as get_supplier_profile or search_awards, so the agent has to infer the boundaries.

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