Skip to main content
Glama

find_similar

指定シャフトに似たスペックの現行モデルを探す。廃盤シャフトの代替探しにも使える。

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": "find_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes基準となるシャフトのID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one meaningful behavioral trait: results are limited to currently available models, so discontinued items are excluded from the output. It says nothing about result count, how similarity is ranked, or what happens when the ID is unknown or refers to a discontinued shaft.

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 short sentences, zero filler, with the core action stated first and the secondary use case following. Nothing is redundant with the tool name or with the schema.

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?

For a single-parameter lookup with no output schema, the description covers what it does, what class of results to expect, and a practical use case. The remaining gaps — result volume and similarity criteria — are minor but would matter to an agent deciding whether one call suffices.

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 parameter 'id' is already documented as the reference shaft ID, which matches the description's phrase about the specified shaft. The description adds no format, range, or lookup-caveat information beyond the schema, so the baseline of 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 gives a specific verb and resource: find current models whose specs resemble a given shaft. That distinguishes it from get_shaft (retrieve one shaft) and search_shafts (query-based search) without needing to open a schema. It stops short of naming or explicitly contrasting any sibling.

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?

One concrete usage scenario is stated — finding replacements for discontinued shafts — which is genuinely useful routing context. However, there is no guidance on when NOT to use it (e.g. when the user wants an exact model, or wants recommendations for a golfer rather than for a shaft), and no alternatives are named despite relevant siblings existing.

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