Skip to main content
Glama

get_markets

Read-only

Read partial player thresholds from a granted source: PrizePicks, Underdog, DraftKings Pick6 or FanDuel props. odds is null; preserve observation timestamps.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sourceNoprizepicks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds genuinely non-obvious behavior: returned odds are null and observation timestamps must be preserved. The 'granted source' phrasing also flags an access/entitlement prerequisite. It stops short of describing pagination or result shape, which keeps it at 4.

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 sentences, no filler, and the core action and source list are front-loaded. The compressed jargon ('partial player thresholds', 'granted source') costs a bit of immediacy but nothing is wasted.

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?

With no output schema and only two parameters, the description covers the essentials of what is read and one notable output quirk. However, 'partial' is never defined, the limit/pagination contract is absent, and the entitlements implied by 'granted' are not spelled out, leaving real gaps for an agent calling it cold.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It names the four valid source values (helpful, though redundant with the enum) but never mentions the 'limit' parameter, its default of 50, or its 1-200 range, leaving half the parameters unexplained anywhere.

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 gives a specific verb ('Read') and resource ('partial player thresholds') and enumerates the four source values, which maps directly onto the source enum. It is somewhat jargon-heavy ('partial player thresholds', 'granted source') and does not explicitly distinguish itself from siblings like get_player_props or get_fanduel_markets, so a 4 rather than a 5.

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 statement of when to use this tool versus alternatives, only a constraint that the source must be 'granted' (an entitlement hint). An agent gets no routing guidance against get_player_props, get_fanduel_markets, or get_prop_history.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.