Skip to main content
Glama

search_shafts

シャフト名やメーカー名でゴルフシャフトを検索する。廃盤モデルも含む。

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": {
      "query": "<query>"
    },
    "name": "search_shafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes検索クエリ(例: Diamana PD, Fujikura)
categoryNoカテゴリdriver

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden. It does add one genuinely useful behavioral fact — that discontinued models are included in results — but says nothing about result limits, pagination, ordering, matching behavior, or what a returned shaft looks like.

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 tight sentences with the searchable fields front-loaded and the result-scope note second. No filler or redundancy.

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 two-parameter search tool with no output schema to explain, the essentials are present, but the description never says what comes back — full shaft records versus identifiers needing get_shaft — which matters given the sibling set.

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%, so both parameters are already documented with an example and an enum. The description reinforces that query takes a shaft name or a manufacturer name, but adds nothing about the category parameter or how query matching works beyond the schema.

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: searching golf shafts, keyed on shaft name or manufacturer name. The added scope note that discontinued models are included further sharpens what the tool covers, though no sibling (e.g. get_shaft) is named or contrasted.

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?

Usage is only implied by the phrase 'search by shaft name or manufacturer name'. There is no statement of when to choose this over get_shaft or recommend_for_golfer, no prerequisites, and no exclusions.

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