Skip to main content
Glama

recommend_for_golfer

ゴルファーの条件(カテゴリ・重量帯・悩み・HS)から最適な現行シャフトを提案する。現行品のみ返す。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recommend_for_golfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
flexNoフレックス(R/SR/S/X)。不明なら省略
categoryNoクラブカテゴリdriver
kickPointNo調子mid
weightMaxNo重量上限(g)
weightMinNo重量下限(g)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It discloses one useful trait — results are restricted to current (non-discontinued) products — but says nothing about how many results come back, whether they are ranked, whether it is a pure read operation, or how matching is scored, which matters a lot for a recommendation tool.

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 with the core action front-loaded and the scope qualifier second. Nothing is wasted, though the brevity is partly the cause of the missing guidance and the phantom parameter references.

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?

For a five-parameter recommendation tool with no annotations and no output schema, the description is too thin: it does not explain what a 'recommendation' result contains, how many items, whether it is ordered, or what happens when criteria cannot be matched. The mismatch between the named inputs and the actual schema further undercuts completeness.

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 coverage is 100%, so the inputs are already documented, but the description actively introduces concepts not present in the schema: 悩み (concerns/issue) and HS (head speed) are listed as inputs yet no such properties exist. This creates a mismatch that could lead an agent to search for parameters that aren't there, instead of clarifying the five real ones (flex, category, kickPoint, weightMin, weightMax).

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 action — proposing the optimal current shaft (現行シャフトを提案する) — from golfer attributes, and adds a scope qualifier ('現行品のみ返す' / returns only current products) that hints at a difference from search_shafts. It does not name any sibling explicitly, so an agent must infer the boundary from context rather than from the text.

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?

There is no explicit when-to-use or when-not-to-use guidance relative to find_similar, get_shaft, or search_shafts. The only usage signal is the implicit 'give golfer conditions, get a recommendation', leaving the agent to guess whether this is a discovery tool or a lookup tool.

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