puntersedge

One horse's runs in our results

horse_runs

Read-onlyIdempotent

Every run one thoroughbred has in PuntersEdge's own settled results, newest first: venue, date, distance, barrier, jockey, weight, finishing position, margin and starting price. Built from our results rather than Racing Australia, so it answers when horse_form cannot. Name the horse as our results spell it, or by the pe: reference other tools return. 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": {
      "horse": "<horse>"
    },
    "name": "horse_runs"
  }
}

Input Schema

Name	Required	Description	Default
`horse`	Yes
`limit`	No

Output Schema

Name	Required	Description	Default
`data`	Yes	The API response, with links and empty fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish this is a safe, idempotent read, so the description's real contribution is the cost ('3 credits'), plan availability ('Every plan'), result ordering ('newest first') and the data provenance. Those are behaviors the annotations cannot express, though it says nothing about result volume or empty-result behavior.

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 dense sentences, front-loaded with purpose before sibling contrast and cost. The enumerated field list partly duplicates what the output schema already exposes, which is the only real waste.

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?

An output schema exists, so return fields need not be re-explained, and the description still covers provenance, ordering, cost, plan gating and identifier syntax. For a two-parameter read tool this gives an agent everything needed to call it correctly except the limit semantics.

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?

Schema description coverage is 0%, so the description must carry the parameters. It meaningfully specifies the horse identifier formats, but the limit parameter (default 10, max 50) is never mentioned, leaving half the parameters undocumented in both places.

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?

The description states a specific verb and resource ('every run one thoroughbred has in PuntersEdge's own settled results') plus the scope and field set returned. It explicitly separates itself from horse_form by naming the data source difference, so an agent can distinguish it from the sibling without reading 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?

It gives a clear selection rule ('answers when horse_form cannot') and tells the caller how to identify the horse (exact spelling or a pe: reference from other tools). There is no explicit statement of when not to use it, such as for unraced or interstate-only horses, so it stops short of a full routing guide.

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

All puntersedge tools Inspect

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.