Skip to main content
Glama
prizepicksapi-mcp

prizepicksapi-mcp

credit_cost

Read-only

Estimate the PrizePicks API credits a REST request path will consume before execution and list available plans; no key needed.

Instructions

Quote how many credits a REST request path costs before running it, plus the plan list. 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": {
      "path": "<path>"
    },
    "name": "credit_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRequest path with query, for example /api/v1/projections?league=NBA&limit=200

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is partly covered. The description adds genuinely new context: 'No key' tells the agent no authentication is needed, and 'before running it' signals the quote has no side effects or charge. It omits what the quote response contains beyond a plan list, which keeps it from a 5.

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?

Two short clauses, front-loaded with the main action. Nothing is wasted, though 'plus the plan list' is terse to the point of ambiguity about what is returned.

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 quoting tool, the description covers the core purpose and auth posture. Since there is no output schema, the description should clarify what a quote looks like (single number, breakdown, units) and what the 'plan list' actually is; that gap keeps it at 3.

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?

With a single parameter at 100% schema coverage, the schema already explains the path format with a concrete example. The description reinforces that the value is a REST request path including query, but adds no syntax or edge-case detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource: quoting the credit cost of a REST request path prior to execution, plus returning a plan list. This is clearly distinguishable from the demo_* and payout_table siblings. The trailing 'plus the plan list' is slightly cryptic but does not obscure the primary function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'before running it' implies a pre-flight cost check, which is useful implied usage. However, there is no explicit guidance on when to skip this tool, whether a quote is required before other calls, or how it relates to any cost-consuming sibling.

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