Skip to main content
Glama
Sign In

puntersedge

by io.github.Propertyscout001
OverviewDiscussionsAdmin

Form for a whole greyhound field

greyhound_field
Read-onlyIdempotent

Every dog in one greyhound race with its recent runs and record, from PuntersEdge's own results. Australian races, and British and Irish ones from 12 October 2026. Give race_id, or venue + meeting_date + race_number. Costs 3 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": "greyhound_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
runsNoRecent runs per dog. The record covers every run held either way.
venueNoVenue name as the feeds spell it, case-insensitive, e.g. Randwick or Sandown Hillside.
race_idNorace_id from odds_board, race_card, race_results or the archive. The most reliable way to name a race.
race_numberNo
meeting_dateNoMeeting day, YYYY-MM-DD, Australian Eastern time.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld). The description adds meaningful context beyond them: data source (PuntersEdge results), geographic/time coverage (Australia, UK/Ireland from 12 Oct 2026), cost (3 credits), and plan availability (Every plan).

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 tight sentences, front-loaded with the core purpose, then coverage, invocation pattern, and cost. No wasted words; every clause carries operational information.

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?

With an output schema present and annotations covering safety, the description is largely complete. It covers source, coverage, cost, and identification, but leaves some ambiguity around whether an identifier is effectively required despite zero required parameters.

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 high at 80%, so most parameters are already documented. The description adds a key disambiguation not present in the schema: race can be identified either by race_id or by venue + meeting_date + race_number, which helps an agent choose the right combination.

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 the resource: every dog in one greyhound race with recent runs and record. The scope (whole field vs. a single dog) implicitly distinguishes it from greyhound_form, but it never names that sibling explicitly.

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

Usage Guidelines3/5

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

It explains how to identify a race (race_id or venue + meeting_date + race_number) but does not say when to use this tool versus greyhound_form or other form-related siblings. Usage is implied by the scope rather than explicitly guided.

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