Skip to main content
Glama
prizepicksapi-mcp

prizepicksapi-mcp

demo_changes

Read-only

Preview fictional change-feed events such as offer.changed from the live schema without an API key. Filter by league and paginate results with limit and cursor.

Instructions

Fictional change-feed events (offer.changed etc.) in the live schema. 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_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page.
cursorNoCursor.
leagueNoLeague code, for example NBA, NFL, NHL, CFB, SOCCER. Comma-separate several.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 real value by disclosing that events are fictional and that no key is required, but 'No key' is ambiguous (no auth key vs. no key field) and nothing is said about ordering, retention, or how the feed updates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the core fact, but it is telegraphic fragments rather than sentences, and the ambiguous 'No key' phrase costs more clarity than it saves space.

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 three-parameter read-only demo feed with no output schema, the agent knows the data is fictional and auth-free, which is the essentials. However, return shape and pagination behavior go unexplained, leaving gaps for an open-world feed tool.

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 limit, cursor, and league all documented, so the baseline is 3. The description adds no extra meaning about paging through the feed or how cursor interacts with limit, and the league filter is never mentioned.

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 a resource (fictional change-feed events such as offer.changed) and implies a read/feed operation, but never states a verb and never distinguishes it from siblings like demo_line_history. 'Fictional' usefully flags that the data is synthetic demo data, yet 'in the live schema' and 'No key' are too compressed to parse confidently.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as demo_line_history or demo_projections. The agent is left to infer usage entirely from the tool name and the sibling list.

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