Skip to main content
Glama

入札案件観測所

入札予定(発注の見通し)を探す

search_bid_plans
Read-onlyIdempotent

Use this when the user asks what public works, services or goods Japanese buyers plan to put out to tender in the coming months (発注の見通し), before the tender notice is published. Returns up to 10 planned procurements, soonest period first, with the total count and counts per quarter. Periods are as published by the buyer (Japanese fiscal year starts in April). For tenders already open, use search_bid_notices. 入札予定・発注の見通し・発注予定(工事・委託・物品役務)

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_bid_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoPrefecture. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
kindNo工事 = construction works, 委託 = consulting/survey/design and other outsourcing, 物品役務 = goods and services
buyerNoProcuring entity: name (part of it is fine) or a buyer_id from resolve_names / get_buyer_profile
limitNoRows per page, 1-10 (default 10)
cursorNonext_cursor from the previous result, with the same other arguments. Up to 3 pages.
keywordNoWords in the title, buyer, department, work type or place. Space = AND. Example: 舗装 修繕
quarterNoQuarter of the fiscal year: 1 = Apr-Jun, 2 = Jul-Sep, 3 = Oct-Dec, 4 = Jan-Mar. Without fiscal_year and quarter, plans from the current quarter on are returned (and those with no period given).
fiscal_yearNoJapanese fiscal year (April to March), e.g. 2026 = 2026-04 to 2027-03
response_formatNoconcise (default): fewer fields per row. detailed: adds IDs, method, original URL and retrieval date per row.
include_announcedNotrue: also return plans whose tender notice has already been published (with a link to it). Default false.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
hintsNo
todayYes
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
appliedYes
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
resultsYes
returnedYes
retrievedYes
by_quarterNo
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.
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / hints / items / properties / try_keyword
      Added value: +{
      +  "description": "A different wording of the keyword (synonym) and how many records it matches; call again with keyword set to this",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/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, so the safety profile is covered. The description adds behavior beyond that: result cardinality ('up to 10'), ordering ('soonest period first'), and aggregate counts per quarter. It stops short of describing pagination depth or the concise-vs-detailed payload difference, which live in the schema.

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 usage trigger, then output shape, then the alternative — a sensible order with no filler sentences. The trailing Japanese keyword list (入札予定・発注の見通し・発注予定…) is padding, though it plausibly aids Japanese query matching.

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 10-parameter, zero-required search tool with an output schema and full annotations, the description covers purpose, when to use, the alternative, default scoping, ordering, and result size. Nothing an agent needs in order to call it correctly is missing.

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 every parameter is already documented, including the fiscal-year-start note and the default 'current quarter on' scoping. The description's parenthetical about the April fiscal year largely restates the schema, so baseline 3 applies with no meaningful added parameter meaning.

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 and resource ('what public works, services or goods Japanese buyers plan to put out to tender'), names the domain concept in Japanese (発注の見通し), and explicitly separates it from the sibling search_bid_notices for already-published tenders. An agent can select this without opening the 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 an explicit when-to-use trigger ('user asks what ... buyers plan to put out to tender in the coming months, before the tender notice is published') and names the alternative plus the condition that selects it ('For tenders already open, use search_bid_notices'). No inference required.

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