Skip to main content
Glama
Sign In

jp-biz-opportunity

by io.github.kodandy
OverviewDiscussionsAdmin

Search Japanese open tender notices (入札公告)

search_open_tenders

FREE — returns live data. Search nationwide Japanese public-sector tender notices (官公需情報ポータルサイト検索API) by keyword: title, agency, region, category, notice text excerpt and the original document URL. keyword (min 2 chars) is required; region is folded into the query. Attribution included.

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

Input Schema

NameRequiredDescriptionDefault
regionNoRegion filter, e.g. tohoku, kanto
keywordNoFree-text keyword, e.g. 空調 or AI チャットボット
deadline_within_daysNoOnly tenders whose submission deadline falls within N days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided; description adds minimal behavioral context ('FREE — returns live data', 'Attribution included') but does not disclose side effects, data freshness, or whether it is a destructive/mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise (two sentences), front-loads key information (FREE, live data), and avoids unnecessary words. Every sentence earns 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?

Given 3 parameters and no output schema, description covers search functionality well, mentioning keyword, region, and deadline filter, and states return includes notice text excerpt and URL. Could mention pagination or result count for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds meaningful context beyond schema: keyword is required (min 2 chars) and region is folded into the query, clarifying parameter usage.

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?

Description clearly states the tool searches Japanese public-sector tender notices by keyword, specifying the resource (tender notices) and verb (search). It distinguishes from siblings by focusing on open tenders.

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?

Description mentions 'FREE — returns live data' and provides usage hints like keyword minimum 2 chars and region folded into query, but does not explicitly state when to use vs alternatives or 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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources