Skip to main content
Glama

入札案件観測所

企業の落札実績の要約

get_supplier_profile
Read-onlyIdempotent

Summary of one company's public-sector award record in Japan: counts by year and category, main buyers, and recent awards. Accepts a company name or the 13-digit corporate number (法人番号). Corporations only; individuals and joint ventures are excluded. 落札企業・受注実績・競合

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": {
      "supplier": "<supplier>"
    },
    "name": "get_supplier_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoPrefecture of the head office, to tell same-name companies apart. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
supplierYesCompany name as the user wrote it (legal form such as 株式会社 may be omitted), 13-digit corporate number, or supplier_id. A name matching several companies returns candidates
response_formatNoconcise (default): fewer fields per row. detailed: adds IDs, method, original URL and retrieval date per row.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameNo
noteYes
foundYes
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
aliasesNo
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
ambiguousNo
confirmedNo
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.
top_buyersNo
supplier_idNo
awards_totalNo
recent_awardsNo
awards_by_yearNo
corporate_numberNo
awards_by_categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that: the aggregate shape of the response (year/category counts, main buyers, recent awards) and the entity-type exclusion for individuals and JVs, which is a behavioral limit an agent must know before calling.

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 payload content is front-loaded in the first sentence, followed by input and exclusion constraints in two short clauses. The trailing Japanese keyword string ('落札企業・受注実績・競合') reads as search metadata rather than agent-facing guidance and is the one element that does not fully earn its place.

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 a rich annotation set, a full output schema, and 100% schema coverage, the description only needs to convey scope, accepted inputs, and eligibility limits, all of which it does. The remaining gap is the absence of any explicit hand-off to the sibling tools for listing individual awards or resolving ambiguous names.

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 all three parameters (supplier, area, response_format) are already documented in the schema. The description only restates that a company name or 13-digit corporate number is accepted, adding no syntax or interpretation detail for area or response_format. Baseline 3 applies when the schema carries the load.

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 resource and scope: 'Summary of one company's public-sector award record in Japan', and enumerates the content (counts by year and category, main buyers, recent awards). This separates it from the buyer-side sibling get_buyer_profile by implication, but it never explicitly routes the agent between the two, so it stops short of 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?

It supplies a subject-matter constraint ('Corporations only; individuals and joint ventures are excluded') which tells the agent when this tool is not applicable, and states the accepted identifiers. However, there is no explicit guidance on when to pick this over siblings such as search_awards (individual award rows) or resolve_names (disambiguation), so the usage rule must be inferred.

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