Skip to main content
Glama

get_outrights

Read-only

Read stored FanDuel futures market metadata and selection counts without selection prices. Source-native IDs, bounded keyset pages, no frozen snapshot or settlement verification.

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_outrights"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
familyNo
leagueNo
statusNo
event_idNo
market_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly=true, destructive=false, openWorld=false, so the safety bar is low; the description still adds real value with bounded keyset pagination, source-native ID provenance, and the caveat that results are not a frozen snapshot and carry no settlement verification. It stops short of describing ordering or what happens when filters combine, but the freshness and pagination disclosures are substantive.

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?

A single dense sentence with the resource stated first and the exclusions trailing; no filler, no restatement of the tool name.

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 7-parameter, zero-coverage filter tool with no output schema, the description covers purpose and behavior but leaves the filter surface undocumented. An agent knows what the tool returns conceptually but not how to construct a query with the available fields.

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 coverage is 0% across 7 parameters, so the description must carry all parameter meaning, and it does not. 'Bounded keyset pages' loosely gestures at the after/limit cursor, but family, league, status, event_id, and market_id receive no explanation of accepted values or filtering behavior, and the open/suspended/closed/removed enum is left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Read stored FanDuel futures market metadata and selection counts.' The qualifier 'without selection prices' immediately separates it from a price-returning sibling such as get_outright_odds, so an agent can route without opening either schema.

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

Usage Guidelines4/5

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

The scope boundary 'without selection prices' gives a clear condition for choosing this over a pricing tool, and 'no frozen snapshot or settlement verification' signals when it is not appropriate. It never names an alternative explicitly, so the routing is inferred rather than stated.

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.