Skip to main content
Glama
Sign In

puntersedge

by io.github.Propertyscout001
OverviewDiscussionsAdmin

Live racing sample (no key)

racing_sample
Read-onlyIdempotent

A small live sample of the next races with a few bookmakers' win prices, to see the data before you connect a key. Free. Needs no API key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteYes
racesYes

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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add what they don't say: that this is a small, live, partial subset and that no API key or payment is required. It does not quantify the sample size or note any rate limiting on this no-key path, which is the only real gap.

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?

Three short, front-loaded sentences that lead with what the tool returns. 'Free. Needs no API key.' slightly re-states the same access point already implied by 'before you connect a key', a minor redundancy.

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 preview tool with an output schema that documents the return shape, the description gives enough to call it correctly and to know why an agent would pick it. Missing only the sample's rough size, which would help an agent judge whether it is sufficient for the task.

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?

The schema takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the sample is fixed-shape rather than filterable.

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?

States a concrete verb and resource: a live sample of the next races with a few bookmakers' win prices. The word 'sample' plus 'before you connect a key' distinguishes it from full-data siblings like race_odds or odds_board, though no sibling is named explicitly.

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?

'to see the data before you connect a key' gives a clear condition for selecting this tool over the authenticated full-data tools. It stops short of naming the alternative tools or stating an explicit 'use X instead once you have a key', so it is clear context rather than a full routing rule.

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