Skip to main content
Glama

Capper record

capper_record
Read-onlyIdempotent

One sports capper's record, looked up by X (Twitter) handle: wins, losses and units over the last 30 days on the picks Slipstream tracks, dated, with their place on the standings and a link to their page. Use it when someone asks whether a capper is winning or what their record is. A handle Slipstream does not track returns a link to the standings.

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": {
      "handle": "<handle>"
    },
    "name": "capper_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe capper's X handle, with or without the @.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world. The description adds real substance beyond them: the 30-day window, that it covers only picks Slipstream tracks, the dated per-pick nature and the standings/link fields, plus the untracked-handle fallback. No pagination, rate limit, or error detail is given, which keeps it below a 5.

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 preceded by the return summary; the scope and payload are front-loaded and the usage trigger plus edge case follow. No filler or repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-shape burden and does so: what fields come back, the time window, and what happens for an untracked handle. For a single-parameter read tool with annotations covering safety, nothing essential for correct invocation is missing.

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?

Only one parameter, and the schema already documents it at 100% coverage including the 'with or without the @' detail. The description adds the meaning of the handle (X/Twitter identity) and the untracked-handle behavior but nothing about format beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('one sports capper's record, looked up by X handle') and enumerates the payload: wins, losses, units over the last 30 days, dates, standings position and page link. That is clearly distinct from siblings like capper_standings or capper_open_picks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger: 'Use it when someone asks whether a capper is winning or what their record is.' It also handles the untracked-handle case by routing to the standings. It stops short of naming a sibling directly as the alternative, so it is clear context rather than full when/when-not routing.

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