Skip to main content
Glama

Tonight's consensus

tonights_consensus
Read-onlyIdempotent

Tonight's games where the sports cappers Slipstream ranks agree, with how many cappers are on each game and how they split. Use it when someone asks what cappers are on tonight or where they agree. Takes an optional league. The sides themselves and the cappers on them are not returned.

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

Input Schema

NameRequiredDescriptionDefault
sportNoA league, like "NBA", "NFL", "NCAAF" or "NHL". Leave out for every league.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely useful output-scope disclosure (consensus games, capper counts, splits, and the deliberate omission of sides and capper names). It stops short of noting edge cases such as what happens on nights with no agreeing games.

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 short sentences, purpose front-loaded, followed by usage trigger and output exclusions. 'Takes an optional league' marginally restates the optional schema field but is cheap and clarifying.

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 burden of describing returns and does so: agreed games, capper counts, the split, and what is excluded. Combined with annotations and a fully documented single parameter, an agent has everything needed to select and call it.

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 coverage is 100% and the single parameter is already documented with league examples, so baseline would be 3. The description adds that the league filter is optional and scoping is league-level, reinforcing the schema's 'Leave out for every league' default without contradicting it.

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 resource (tonight's games where Slipstream-ranked cappers agree) plus the payload shape (capper counts and how they split). The explicit note that sides and capper identities are not returned cleanly separates it from siblings like open_sides and 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 a concrete trigger: 'Use it when someone asks what cappers are on tonight or where they agree.' That is clear routing context, but it does not name an alternative tool or a when-not-to-use condition.

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