Skip to main content
Glama

get_shaft

IDを指定して1本のゴルフシャフトの詳細スペックを取得する。

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": {
      "id": "<id>"
    },
    "name": "get_shaft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesシャフトID(search_shaftsで取得可能)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden; '取得する' does imply a non-mutating read, which is useful. However, it says nothing about what happens when the ID does not exist, what '詳細スペック' contains in shape or depth, or whether the lookup is cached/rate-limited.

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?

One short sentence with the action and the resource front-loaded and no filler. It could have been a 5 had the sentence also carried the search-then-fetch relationship, but as written it is efficient and unambiguous.

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-only lookup with no output schema, the description covers the essential contract. The gap is that '詳細スペック' is left undefined and not-found behavior is unaddressed, which matters because neither annotations nor an output schema fill those holes.

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 single id parameter is already documented, including how to obtain it. The description's 'IDを指定して' restates the schema rather than adding format, range, or fallback meaning, so the baseline 3 applies.

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 ('取得する' / retrieve) and a specific resource ('1本のゴルフシャフトの詳細スペック'), scoped by ID. An agent can distinguish this single-record lookup from the sibling search_shafts by the wording alone, though the description never names the alternative explicitly.

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 description offers no when-to-use or when-not-to-use guidance and no prerequisites. The only routing hint ('search_shaftsで取得可能') lives in the input schema's id field, not in the description, so the description itself does nothing to steer an agent away from search_shafts or find_similar.

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