Skip to main content
Glama

Japan Ground Network public synthetic sandbox

jgn_get_demo_worker

Read-onlyIdempotent

Read a fictional operator fixture. Not real identity, skills verification, history 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": {
      "worker_id": "<worker_id>"
    },
    "name": "jgn_get_demo_worker"
  }
}

Input Schema

NameRequiredDescriptionDefault
worker_idYes

Output Schema

NameRequiredDescriptionDefault
workerYes
environmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the safety profile is settled elsewhere. The description adds genuinely new behavioral context by declaring the returned data is synthetic and must not be read as real identity, skills verification, history or availability — a caveat an agent could not derive from structured fields. Minor gaps remain (no error behavior for a missing ID), but that is covered by the enum constraint.

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?

Two sentences, front-loaded with the action and immediately followed by the negative scope. Every clause carries information; nothing is redundant.

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 an output schema present, return structure need not be described, and annotations carry the safety profile. For a single enumerated parameter the definition is nearly sufficient; the only shortfall is that it never names the worker_id input or the lookup semantics.

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 0%, and the description never mentions the single worker_id parameter or its two allowed values. The enum values ('demo-operator-a', 'demo-operator-b') are largely self-explanatory, which keeps this at a minimum-viable 3 rather than lower, but the description contributes nothing beyond the schema here.

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?

States a verb ('Read') and a resource ('fictional operator fixture'), and the clarifying phrase 'Not real identity, skills verification, history or availability' sharpens the scope. However, 'fixture' is jargon and the description never says what a worker record actually contains or that it is looked up by ID, so the purpose is only implied by the tool name rather than fully spelled out.

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?

The 'fictional' framing implies demo/sandbox usage, but there is no explicit when-to-use statement, no mention of the sibling jgn_search_demo_workers for discovery, and no guidance on picking between the two enum values. An agent gets a hint of context but no routing rule.

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