Skip to main content
Glama

jp-biz-opportunity

by io.github.kodandy

Open tender notice raw record (入札公告 detail)

get_tender_notice

Full raw record of one Japanese public-sector open tender notice: agency, region, category, publication date, submission deadline and specification summary. Paid via x402: each call costs 0.05 USDC. This tool returns the HTTP 402 payment challenge for the resource. Private beta note: a successful settlement is acknowledged with a receipt that records your priority access; the dataset itself unlocks for early settlers as provisioning goes live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tender_idYesTender notice ID in the form T-2026-NNNN, e.g. T-2026-0117

TDQS

A4.2/5.0
Behavior5/5

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

Without annotations, the description fully discloses the payment requirement, HTTP 402 response, beta limitations, and settlement process. This is critical behavioral information beyond a simple retrieval tool.

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 description is four sentences, front-loading purpose then adding payment and beta details. Each sentence is relevant, though the beta note could be shortened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, parameters, and payment, but lacks response format details (e.g., exact fields returned, error cases). With no output schema, describing the response would improve completeness.

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?

The input schema has 100% coverage with a description for tender_id. The tool description adds no extra parameter meaning, so baseline 3 is appropriate.

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?

The description clearly states it retrieves the full raw record of a Japanese public-sector open tender notice, listing key fields. It distinguishes itself from sibling search tools by focusing on a single record detail.

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?

The description explains the paid access model (0.05 USDC per call, HTTP 402 challenge) and notes the private beta, giving clear context for when to use. However, it does not explicitly compare to alternatives or state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All jp-biz-opportunity toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct operation: catalog listing, free search for subsidies/tenders/sanctions, and paid detail retrieval for subsidies/tenders. No ambiguity between tools.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern: 'list_' for catalog, 'search_' for free queries, and 'get_' for paid detail retrievals. The pattern is predictable and clear.

Tool Count5/5

Six tools cover the core needs: listing available datasets, searching three categories (subsidies, tenders, sanctions), and retrieving full records for two of them. This is well-scoped for a specialized gateway.

Completeness4/5

The set covers search and detail retrieval for subsidies and tenders, plus sanctions search. Missing a 'get_sanction' tool for full sanctions records, but the search tool returns sufficient data for most use cases. The paid detail tools currently only initiate payment, but that is by design in private beta.

Resources