Skip to main content
Glama

Capper standings

capper_standings
Read-onlyIdempotent

The sports cappers who are up the most units, ranked, with each one's record, units and page, tracked from their public posts on X (Twitter). Use it when someone asks which cappers are winning, who leads a league or who is hot right now. Takes an optional league (NBA, NFL, college football, NHL) and a window of 30 or 7 days. Only cappers who are up over the window are named.

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

Input Schema

NameRequiredDescriptionDefault
sportNoA league, like "NBA", "NFL", "NCAAF" or "NHL". Leave out for every league.
window_daysNoThe window in days. 30 when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the data derives from public X posts, and only cappers who are up over the window appear, which explains why the result set can be short or empty. Pagination or result-size limits are not mentioned, which is the remaining gap.

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?

Three sentences, front-loaded with what the tool returns, then when to use it, then the key filtering caveat. No filler, and the most surprising constraint (only profitable cappers listed) is placed where it is easy to catch.

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 low-complexity, two-optional-parameter read tool with full schema coverage and no output schema, the description supplies enough: what is ranked, what fields come back, when to call it, and the positive-units filter. It stops short of noting result limits or ranking ties, which would make it fully self-sufficient.

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 coverage is 100%, so both parameters are already documented, including the enum and the 30-day default. The description only moderately enriches this by spelling out 'college football' as the plain-language form of NCAAF and tying the window to the 'up over the window' filter. That is a marginal addition over the schema, consistent with the baseline 3.

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 names a specific resource and output shape: a ranked leaderboard of sports cappers by units, with record, units and page, sourced from public posts on X. That is far more than a restatement of the name. It does not explicitly contrast itself with siblings like capper_record or capper_open_picks, so an agent must infer the leaderboard-vs-individual distinction.

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?

Concrete trigger phrases are given: 'which cappers are winning', 'who leads a league', 'who is hot right now'. This tells the agent the intent category clearly. There are no explicit exclusions or named alternatives (e.g., 'for a single capper's history use capper_record'), so the retrieval routing is implied rather than stated.

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