Skip to main content
Glama

PlugRail JP Recall

get_recall_detail

Read-onlyIdempotent

管理番号(11桁)からリコール詳細1件を取得します。入力例: {"management_number": "00000035877"}

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": {
      "management_number": "<management_number>"
    },
    "name": "get_recall_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
management_numberYes11桁の管理番号。例: "00000035877"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / management_number / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
    • removedInput schema / properties / management_number / type
      Removed value: -"string"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the behavioral burden on the description is light. The description adds only the 11-digit identifier constraint and single-record scope, and remains silent on what a lookup miss returns or what fields the detail contains.

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 short sentences, front-loaded with the action and resource, with zero filler. The inline JSON example is somewhat redundant with the schema's own example, costing a small amount of conciseness.

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?

For a one-parameter read tool with full schema coverage and rich annotations, the description is largely sufficient to invoke it correctly. With no output schema, though, it gives no hint of what a 'recall detail' contains or how a not-found result surfaces, leaving a real gap.

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 100%, and the schema already documents the management_number parameter as an 11-digit value with the example "00000035877". The description's example and digit-count note repeat the schema rather than adding new meaning such as accepted numeric-vs-string input handling.

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?

The description states a specific verb and resource: fetch one recall detail record using an 11-digit management number. '詳細1件' implicitly contrasts with its sibling search_recalls, which returns sets of results, but the description never names that sibling or explicitly draws the distinction.

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?

Usage is only implied by the fact that this tool takes a single identifier, so an agent can infer it is for looking up a known record. There is no explicit 'use this when you already have the management number, use search_recalls when you don't' guidance or any stated preconditions.

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.