Skip to main content
Glama

Analyse golf bag gaps

nymrel_golf_bag_gap
Read-only

Analyse carry-distance gaps for a structured list of golf clubs.

Every club needs a name and its measured carry_distance_yards; loft_degrees is optional. Pass 1 to 14 clubs with non-blank names, unique ignoring letter case and surrounding spaces. The upstream rejects any other key, so send only these three. Invalid counts or names are rejected before contacting the upstream; correct them instead of retrying.

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": {
      "clubs": "<clubs>"
    },
    "name": "nymrel_golf_bag_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
clubsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / clubs / items / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / clubs / items / properties / name / pattern
      Added value: +"\\S"
    • addedInput schema / properties / clubs / maxItems
      Added value: +14
    • addedInput schema / properties / clubs / minItems
      Added value: +1
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: invalid counts or names are rejected locally before the upstream is contacted, and the upstream enforces a strict key whitelist. The instruction to correct errors rather than retry is valuable remediation context an agent would not otherwise know.

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?

Four tight sentences, purpose front-loaded, followed by the input contract and then the error-handling rule in the position where it matters. Little waste; the count range is duplicated from the schema's minItems/maxItems, which is the only real redundancy.

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?

An output schema exists, so return values need not be explained, and the input contract is fully specified including constraints the schema cannot express. For a single-parameter, read-only analysis tool this is close to sufficient. The one omission is a hint about what the analysis actually reports, which would help an agent judge whether the call answers its question.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% at the top level, so the description must carry the load and largely does: it names the required fields, marks loft_degrees optional, states the 1-14 count range, and adds the case- and whitespace-insensitive uniqueness rule that no JSON Schema keyword expresses. The 'send only these three' warning reinforces the schema's additionalProperties=false in a way an agent reading only the parameter list might miss. Minor deduction for restating minItems/maxItems that the schema already encodes.

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?

Opens with a specific verb and resource: 'Analyse carry-distance gaps for a structured list of golf clubs', which is unambiguous about the operation and its input shape. The sibling tools are all in unrelated domains (website audit, domain lookup, remote file access), so differentiation is trivially satisfied. It stops short of 5 because what a 'gap' means analytically is never characterized.

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?

There is no explicit when-to-use statement, though the purpose sentence implies the trigger well enough. The guidance that does exist is operational: pass 1 to 14 clubs, unique names ignoring case and surrounding whitespace, and only the three permitted keys. No alternatives exist among siblings, so the absence of routing guidance is not a real gap, but the tool-selection rationale is only implied.

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.