Skip to main content
Glama

Japan Ground Network public synthetic sandbox

jgn_preview_request

Read-onlyIdempotent

Validate a fixed synthetic request example against the local request schema. Does not persist a draft, submit, quote, book, pay or dispatch. Only enum selections and bounded integers are accepted.

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": {
      "service_code": "<service_code>",
      "target_id": "<target_id>",
      "worker_id": "<worker_id>",
      "checklist_codes": "<checklist_codes>",
      "budget_cap_jpy": "<budget_cap_jpy>",
      "report_locale": "<report_locale>",
      "access_basis": "<access_basis>"
    },
    "name": "jgn_preview_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_idYes
worker_idYes
access_basisYes
service_codeYes
report_localeYes
budget_cap_jpyYes
checklist_codesYes

Output Schema

NameRequiredDescriptionDefault
paidYes
bookedYes
previewYes
reasonsYes
persistedYes
environmentYes
human_handoffYes
inquiry_guideYes
valid_exampleYes
example_date_onlyYes
local_request_schema_validYes
actual_availability_checkedYes

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 declare readOnly, idempotent, closed-world and non-destructive behavior, and the description is fully consistent with them. It adds real value beyond the annotations by explicitly enumerating what will not happen (no draft persistence, no submit/quote/book/pay/dispatch) and by noting the accepted input class (enum selections and bounded integers).

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?

Three short sentences, front-loaded with the core action, then the non-goals, then the input constraint. The verb list (persist, submit, quote, book, pay, dispatch) is slightly enumerative but each item earns its place by closing off a plausible agent misreading.

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

Completeness2/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, but for a tool with seven required parameters and zero schema description coverage the description says nothing about what each parameter selects or how they relate (e.g. checklist_codes to service_code). An agent can call it but cannot confidently choose values from the prose alone.

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% across seven required parameters, so the description carries the full explanatory burden. It offers only a generic statement that enums and bounded integers are accepted, leaving service_code, target_id, worker_id, checklist_codes, report_locale, access_basis and budget_cap_jpy entirely unexplained beyond their raw enum values.

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?

States a specific verb and resource: validate a fixed synthetic request example against the local request schema. The purpose is unambiguous and clearly distinct from the read-only getter siblings, though no sibling is named as an alternative.

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?

The description scopes usage negatively by ruling out persistence, submission, quoting, booking, payment and dispatch, which usefully routes the agent away from real write paths. However, it never states a positive when-to-use condition or names an alternative tool for the actual submit path.

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