Skip to main content
Glama

Tonight's consensus sides

open_sides
Read-onlyIdempotent

Tonight's consensus sides with the cappers on each. Needs a Slipstream Pro account.

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

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

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds a useful auth prerequisite (Pro account), but says nothing about data freshness, what 'sides' are, or the return format.

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?

The description is two short sentences and front-loads the resource and account prerequisite. The phrase 'with the cappers on each' is vague filler that weakens clarity, but there is no wasted bulk.

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-only tool with full schema coverage and no output schema, this is minimally complete. It still leaves the core concept ('sides') and data freshness unexplained, which an agent would need to invoke confidently.

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?

The single optional 'sport' parameter is fully documented in the schema, including the 'Leave out for every league' behavior. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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

Purpose3/5

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

The description names the resource ('Tonight's consensus sides') but supplies no verb and leaves 'with the cappers on each' ambiguous. It does not distinguish this tool from siblings such as tonights_consensus 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 Guidelines2/5

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

The only usage-related statement is the account prerequisite ('Needs a Slipstream Pro account'). There is no guidance on when to use this versus other consensus or capper tools, and no exclusions.

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