Skip to main content
Glama
Sign In

puntersedge

by io.github.Propertyscout001
OverviewDiscussionsAdmin

North American tote odds

us_tote
Read-onlyIdempotent

TVG's live tote odds for US and Canadian races: per runner the morning line and the current win odds (odds-to-1 and decimal) with the WIN pool behind them. Pari-mutuel, so a pre-race price is an estimate of what the pool will pay; settled payoffs are on race_results with country US. For one race, history adds how the odds and pool moved and exotics adds the probables and will-pays. Costs 2 credits. Every plan.

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

Input Schema

NameRequiredDescriptionDefault
dateNoUS race day, YYYY-MM-DD. Default today in the US.
statusNo
countryNo
exoticsNoNeeds race_id or source_race_id.
historyNoNeeds race_id or source_race_id.
race_idNorace_id from odds_board, race_card, race_results or the archive. The most reliable way to name a race.
source_race_idNoTVG's race key, tvg_<track>_<YYYY-MM-DD>_<n>, for a race no Australian book prices.

Output Schema

NameRequiredDescriptionDefault
dataYesThe API response, with links and empty fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the safety profile is covered. The description adds genuine non-schema context: pari-mutuel nature means pre-race prices are estimates, plus cost ('2 credits') and availability ('Every plan'). It stops short of return/pagination detail, but the output schema covers return shape.

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 dense sentences, front-loaded with the core 'what', followed by behavioral caveat and routing/option guidance. No filler; each sentence carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values needn't be spelled out; the description supplies the pari-mutuel caveat, cost, plan availability, sibling routing, and option semantics — everything needed to call it correctly for a read-only priced-data tool.

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?

Schema coverage is 71% and the description adds semantic value beyond it: history 'adds how the odds and pool moved' and exotics 'adds the probables and will-pays', clarifying what these booleans actually return. Date/country scope is also contextualized ('US and Canadian races'). Meaningfully above the baseline for a well-covered 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 resource (TVG live tote odds for US/Canadian races) and what each runner returns — morning line plus current win odds in odds-to-1 and decimal with WIN pool. It distinguishes itself from race_results (settled payoffs) and implicitly from generic siblings like race_odds/odds_board by naming the source (TVG) and scope (North American pari-mutuel).

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

Usage Guidelines5/5

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

Explicitly routes to alternatives: 'settled payoffs are on race_results with country US' tells the agent when this tool is the wrong choice. It also gives conditions for the history and exotics options ('for one race'). Clear when-to-use and when-to-go-elsewhere.

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

All puntersedge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources