Skip to main content
Glama
Sign In

puntersedge

by io.github.Propertyscout001
OverviewDiscussionsAdmin

Best sports prices

sports_best_odds
Read-onlyIdempotent

The best price for each outcome of a sport's upcoming events and which bookmaker has it. Costs 3 credits. Every plan.

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": {
      "sport_key": "<sport_key>"
    },
    "name": "sports_best_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
sport_keyYesSport key from sports_list, e.g. afl, nrl, nba or soccer_epl. An unknown key is answered with the valid ones.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sport_key / description
      Previous value: -"Sport key from sports_list, e.g. afl, nrl, nba or epl. An unknown key is answered with the valid ones."New value: +"Sport key from sports_list, e.g. afl, nrl, nba or soccer_epl. An unknown key is answered with the valid ones."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description adds useful operational context by stating the credit cost and plan eligibility, but it does not discuss freshness, pagination, or other runtime behavior beyond what the annotations and output schema provide.

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?

The description is front-loaded and extremely compact: it states the returned information first, then cost and plan availability. Every sentence carries operational or descriptive value with no wasted text.

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?

Given the single required parameter, full schema documentation, output schema, and safety annotations, the description is largely complete for invocation. Its main gap is lack of sibling differentiation and usage guidance, but the core purpose and cost are clear.

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?

The schema fully documents the single sport_key parameter, including examples and the behavior for unknown keys. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate for 100% schema description coverage.

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 clearly states what the tool returns: the best price per outcome for a sport's upcoming events and the bookmaker offering it. It is specific about the resource and output, but it does not explicitly distinguish itself from siblings like best_odds or sports_odds.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as sports_odds, best_odds, or odds_board. 'Every plan' and the credit cost are operational facts, not usage conditions or exclusions.

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