Skip to main content
Glama
prizepicksapi-mcp

prizepicksapi-mcp

demo_projections

Read-only

Preview PrizePicks projection data with fictional sample rows that mirror the live schema, so you can learn field names and structure before querying live lines without an API key.

Instructions

Fictional sample PrizePicks projections with the exact live schema (is_demo: true). Use to learn the fields before calling live data. No key.

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

Input Schema

NameRequiredDescriptionDefault
statNoExact market name, for example Points or Pass Yards.
tierNoOnly lines with this tier on a selection.
limitNoRows per page (1-200, or up to 1000 with view=compact).
cursorNometa.next_cursor from the previous page.
leagueNoLeague code, for example NBA, NFL, NHL, CFB, SOCCER. Comma-separate several.
searchNoPlayer name search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two genuinely useful facts beyond that: the data is fictional (so results are not real market lines) and no API key is required. It says nothing about pagination mechanics despite having a cursor parameter, so it stops at adequate-plus.

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?

Three short sentences, front-loaded with what the data is, then the use case, then the auth note. "No key." is a fragment but carries real information for an agent deciding whether it can call it immediately.

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?

All six parameters are optional and fully documented in the schema, and there is no output schema to explain — the phrase "exact live schema" usefully tells the agent the response shape matches the production tool. Minor gap: nothing about result volume or default pagination behavior for a read endpoint.

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% and every parameter carries its own description, including the enum and the compact-view limit exception. The description adds no parameter meaning beyond noting is_demo: true, which is an output field rather than an input, 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 names the resource precisely — fictional Sample PrizePicks projections that mirror the live schema, flagged with is_demo: true. An agent can immediately tell this apart from the live projections call, though no sibling demo tools (demo_changes, demo_line_history) are named for contrast.

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?

"Use to learn the fields before calling live data" gives an explicit when-to-use condition tied to schema discovery. It stops short of stating when not to use it (e.g., do not use demo data for real analysis) or naming the live counterpart, but the intent is unmistakable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.