Skip to main content
Glama
prizepicksapi-mcp

prizepicksapi-mcp

payout_table

Read-only

Retrieves standard PrizePicks Power and Flex payout multipliers with derived break-even probabilities for evaluating entry risk; excludes goblin/demon adjusted lines.

Instructions

Official PrizePicks standard entry payout multipliers (power and flex) with derived break-even probabilities. Real reference data, no key. Goblin, demon and adjusted-odds lines pay differently and are not estimated.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only and open-world; the description adds that this is static reference data needing no API key and that goblin/demon/adjusted lines are excluded rather than estimated, giving the agent useful context about data provenance and scope. It does not describe return structure, but the tool is simple.

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?

Three tight sentences, front-loaded with the primary purpose, followed by data-nature and scope caveats; no redundant wording.

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?

For a zero-parameter reference lookup, the description covers what data is returned, the no-key access, and exclusions for non-standard lines. Without an output schema it could specify the shape of multipliers and break-even values, but the essentials are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no input parameters; the schema is empty and the description correctly adds nothing about parameters, meeting the baseline for zero-param tools.

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 it returns official standard-entry payout multipliers for power and flex plays plus derived break-even probabilities. The resource is specific, though phrased as a noun list rather than a verb-led statement, and it does not reference any sibling tool by name.

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?

No explicit 'use when' or alternative tool is named; guidance is limited to the implied lookup use and the caveat that goblin, demon and adjusted-odds lines pay differently and are not estimated, which functions as a when-not-to-use for those cases.

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