Skip to main content
Glama

入札案件観測所

収録の範囲と更新日

get_coverage
Read-onlyIdempotent

What this server covers and does not cover: counts, period, last update, and which claims the data can and cannot support. Use this before stating that something does not exist. It describes the data set itself (what is included, how recent), not a region's or buyer's activity: for trends, top suppliers or counts of a prefecture, city or agency (e.g. 静岡県 as a buyer), use get_buyer_profile or search_awards. 収録範囲・更新日・網羅性

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": "get_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional prefecture: adds the number of covered buyers and results there. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
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)
awardsYes
buyersYes
sourceYes
can_sayYes
cite_asNoOne-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
relatedNoFacts related to this result (counts) and the tool call that returns them
retrievedYes
cannot_sayYes
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.
open_noticesYes
suppliers_with_profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add semantics — and it does, clarifying that the tool returns dataset-level facts plus supportable/unsupportable claim boundaries rather than activity data. It does not mention whether the coverage figures are cached or how 'last update' is computed, which would have completed the picture.

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-loaded with the core definition, then the usage rule, then the disambiguation — a sensible order. Slightly dense in the middle sentence, and the trailing Japanese title duplicates the title field, but no sentence is wasted.

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 single-optional-parameter metadata tool with an output schema and full annotation coverage, the description supplies everything needed: what it returns conceptually, when to call it, and where to go instead. Return-value detail is correctly omitted because an output schema exists.

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 coverage is 100% and the area parameter's description already enumerates accepted forms (福岡県, 福岡, Fukuoka, 40, national), so the input schema carries the full burden. The description only implies the parameter's purpose ('adds the number of covered buyers and results there' is schema text, not description text), so baseline 3 applies.

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?

States a specific resource — dataset coverage metadata: counts, period, last update, and the claims the data can and cannot support. It explicitly contrasts itself with get_buyer_profile and search_awards, so an agent can tell 'dataset-level coverage' from 'entity-level activity' without opening either schema.

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?

Gives a concrete trigger ('use this before stating that something does not exist') and an explicit exclusion, naming the alternatives to use for trends, top suppliers, or prefecture/city/agency counts with a concrete example (静岡県 as a buyer). Both the when and the when-not are present.

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