Skip to main content
Glama

入札案件観測所

入札公告1件の要点

get_bid_notice
Read-onlyIdempotent

Get the key points of one open tender notice (summary, procedure and deadlines, eligibility, place, period) and the link to the original notice. Use the notice_id from search_bid_notices. Summaries are machine-made; the original document is authoritative. 入札公告の概要・締切・参加資格・原文

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": {
      "notice_id": "<notice_id>"
    },
    "name": "get_bid_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
notice_idYesID from search_bid_notices, e.g. kkj-156722 or ext-4418

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
foundYes
placeNo
titleNo
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)
existsNoWhen found is false: true if the notice exists but is no longer open (access not_public_now), false if no such notice is known
periodNo
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`).
expiredNo
messageNo
relatedNoFacts related to this result (counts) and the tool call that returns them
summaryNo
deadlinesNo
last_dateNo
notice_idNo
procedureNo
retrievedYes
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.
search_urlNo
eligibilityNo
original_urlNo
closed_reasonNo
deadline_noteNo
deadline_kindsNoEach date in deadlines with what it is (participation application, bid submission, opening, question, notification, document issue, briefing, unknown)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond them: summaries are machine-generated and the original document is authoritative, and a link to the original is returned. It does not discuss freshness or how much of the notice body is summarized, keeping it from a 5.

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 primary purpose and returned fields, then the ID source, then the machine-summary caveat. The trailing Japanese fragment largely restates the field list already given in English, which is mild redundancy rather than noise, so it stays efficient but not maximally tight.

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?

An output schema exists, so return-value explanation is not required, and the description still flags the key caveat (machine-made summary, original is authoritative) that an agent needs for trust decisions. For a single-parameter read tool whose annotations cover safety, this is close to complete; only guidance on stale or missing notices is absent.

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?

With a single parameter and 100% schema description coverage, the schema already explains that notice_id comes from search_bid_notices and gives example formats (kkj-156722, ext-4418). The description only repeats the provenance, adding no new meaning such as ID format variants or error behavior for unknown IDs. 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 verb (get) and resource (one open tender notice) and enumerates the returned content: summary, procedure and deadlines, eligibility, place, period, plus a link to the original. The phrasing 'one ... notice' and the reference to notice_id from search_bid_notices clearly separates it from the sibling search tool.

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

Usage Guidelines4/5

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

Explicitly says to use the notice_id obtained from search_bid_notices, which tells the agent this is the follow-up detail call after a search. It does not state exclusions (e.g. when a different detail tool such as get_buyer_profile is more appropriate), so it stops short of full when/when-not guidance.

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