Skip to main content
Glama

A capper's open picks

capper_open_picks
Read-onlyIdempotent

A tracked capper's open picks tonight. Needs a Slipstream Pro account.

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_open_picks"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the Slipstream Pro entitlement requirement and the 'tracked capper' precondition, which are failure conditions an agent should check before calling. It still omits what happens for an untracked handle or whether results are paginated.

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 zero filler, and the resource/scope comes before the access caveat. Slight deduction because the opening is a telegraphic noun phrase rather than a complete statement, and 'tonight' is left undefined (timezone/cutoff).

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

Completeness3/5

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

For a one-parameter read tool this covers the basics, and the entitlement note is a genuine addition. But the key domain term 'open picks' (presumably ungraded/unsettled picks) is never defined, and with no output schema the description offers no hint about the shape or size of what comes back. The description also doesn't say whether a non-tracked handle yields an error or an empty result.

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?

There is a single parameter at 100% schema description coverage, and the schema already explains the X handle format including the optional '@'. The description only implies the handle must belong to a *tracked* capper, which is a mild semantic addition. Baseline 3 is appropriate when the schema carries the parameter definition.

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?

Identifies a specific resource with clear scoping: a *tracked* capper's *open* picks for *tonight*. That distinguishes it from capper_record (historical) and capper_standings (aggregate) without needing their schemas. It falls short of 5 because the phrasing is nominal rather than a verb+resource statement, and it doesn't explicitly name the sibling it differs from.

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?

The prerequisite 'Needs a Slipstream Pro account' is useful context for deciding whether to call at all. However, there is no explicit when-to-use guidance relative to capper_record or open_sides, and no statement of when this tool is the wrong choice. Usage is only implied by the word 'open' and 'tonight'.

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