Skip to main content
Glama

Sample lines (no key)

get_demo_projections
Read-onlyIdempotent

Fictional sample rows in the live response shape, for trying the API without a key. Never present these as real lines.

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

Input Schema

NameRequiredDescriptionDefault
statNoExact machine stat slug
viewNoResponse shape
afterNoAlias for cursor
limitNoPage size. Oversized valid limits are clamped.
sportNoUppercase sport code, or comma-separated codes
cursorNoCursor returned in meta.next_cursor
leagueNoAlias for sport
searchNoPlayer or team search
statusNoRetained rows can be stale; inspect observed_atactive
higher_onlyNoOnly markets with an available higher and unavailable lower side
payout_tierNoMatch a per-side payout tier
start_afterNoInclusive event start bound
start_beforeNoExclusive event start bound
user_requestNoOptional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.
include_predictionNoInclude prediction contracts; excluded by default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the added value here is the disclosure that returned rows are fabricated and must not be surfaced as real data — a genuinely important behavioral trait. It does not say whether the filters/pagination actually operate on the sample set or whether the demo corpus is fixed and small, which are material gaps for a 15-parameter query tool.

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 short sentences, zero filler, with the identity of the data front-loaded and the misuse warning immediately after. Nothing here could be cut without losing meaning.

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 15-parameter tool with rich filtering, the description never says whether those filters, cursor, and limit are honored against the sample data or how large the sample is — knowledge an agent needs to avoid reporting empty or misleading results. Annotations and full schema coverage fill the safety and parameter gaps, keeping this at minimum-viable rather than inadequate.

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 description coverage is 100%, with enums and per-parameter notes (clamping, cursor aliasing, stale-row caveat) already documented in the schema. The description adds no parameter-level meaning at all, so the baseline 3 applies.

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 states a specific resource: fictional sample rows that mirror the live response shape, explicitly framed as a no-key trial path. This is clearly distinguishable from production data, though it never names the sibling (get_projections) that returns real lines, leaving the contrast implicit.

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?

"For trying the API without a key" gives a clear condition for selection, and "Never present these as real lines" sets a firm usage constraint. It stops short of naming an explicit alternative or stating when-not to use it (e.g., once a key exists, use the real endpoint).

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