Skip to main content
Glama

Japan Ground Network public synthetic sandbox

jgn_search_demo_workers

Read-onlyIdempotent

Compare fictional operators for integration testing. These are synthetic fixtures, never real staff or availability.

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": {
      "zone": "<zone>",
      "service_code": "<service_code>"
    },
    "name": "jgn_search_demo_workers"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYes
service_codeYes
budget_cap_jpyNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
environmentYes
real_workersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: all results are synthetic fixtures and never represent real staff or availability, which matters for how an agent should present results. It stops short of saying whether the search is exhaustive, how budget_cap_jpy affects filtering, or what happens when no fixture matches.

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?

Two compact sentences with the synthetic-data caveat front and no filler. It is appropriately sized for a small fixture tool, though the space saved could have been spent on parameter meaning.

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?

An output schema exists, so return values need not be described, and the three-parameter search is simple. Still, with zero parameter documentation the agent must guess the semantics of budget_cap_jpy and cannot tell whether this search is paginated or bounded.

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

Parameters2/5

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

Schema description coverage is 0% and the description names none of the three parameters. The const on zone and the enum on service_code are partly self-explanatory, but budget_cap_jpy (maximum 1,000,000, exclusive minimum 0) is given no meaning at all in either place — is it a filter on price, a hard ceiling, or a ranking hint?

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('compare') and a resource ('fictional operators'), but 'compare' is not the same operation the name promises ('search') and it never says what is returned or how candidates are selected. It does convey the important domain fact that these are synthetic fixtures, yet an agent cannot tell how this differs in behavior from the sibling jgn_get_demo_worker beyond the plural name.

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

Usage Guidelines2/5

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

'for integration testing' is a context, not a when-to-use rule; there is no statement of when to pick this over jgn_get_demo_worker or jgn_list_services. The only real guidance is a negative constraint ('never real staff or availability'), which is useful but not routing 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