Skip to main content
Glama
prizepicksapi-mcp

prizepicksapi-mcp

demo_line_history

Read-only

Retrieve fictional line history for a demo projection ID without an API key, with optional pagination via limit and cursor.

Instructions

Fictional line history for a demo projection id such as demo_nba_001. No key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "demo_line_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDemo projection id.
limitNoRows per page.
cursorNoCursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The description adds useful behavioral context beyond the annotations: the data is fictional and no key is required. However, `No key` is terse and does not clarify authentication expectations or pagination behavior, and the read-only nature is already covered by `readOnlyHint: true`.

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 short and front-loads the purpose before mentioning the no-key behavior. The phrase `No key` is cryptic enough to be slightly wasteful, but overall there is little unnecessary wording.

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 simple demo-data tool with a fully described schema and read-only annotations, the description is mostly adequate. However, with no output schema and no return-format or pagination details, it leaves some context for the agent to infer.

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%, so the schema already documents `id`, `limit`, and `cursor`. The description adds a concrete example for `id` but does not add meaning beyond the schema for `limit` or `cursor`.

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 clearly states that this tool returns fictional line history for a demo projection id, with a concrete example (`demo_nba_001`). It is specific about the resource and data type, though it does not explicitly differentiate itself from siblings such as `demo_projections` or `demo_changes`.

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?

Usage is only implied by mentioning a demo projection id. There is no explicit guidance on when to use this tool versus alternatives, no exclusions, and no explanation of whether it should be used only for demo data.

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