Skip to main content
Glama
Sign In

puntersedge

by io.github.Propertyscout001
OverviewDiscussionsAdmin

One greyhound's form

greyhound_form
Read-onlyIdempotent

One dog's runs from PuntersEdge's own results, newest first: track, distance, box, grade, finishing position, time and margin. By name or the grv:/grsa: reference other tools return (those persist). 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": {
      "dog": "<dog>"
    },
    "name": "greyhound_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
dogYes
limitNo

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description adds useful operational context: the data comes from PuntersEdge's own results, results are newest first, accepted identifiers persist, and calls cost 3 credits on every plan. It does not cover rate limits or authentication, but the annotations already establish read-only, idempotent, open-world, non-destructive behavior.

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 with the core result, then compactly covers return fields, identifier formats, cost, and plan availability. There is no wasted text and the key details are easy to scan.

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 simple two-parameter read tool with an output schema and rich annotations, the description is nearly complete: it explains source, ordering, identifier handling, cost, and plan eligibility. The main gap is that it does not explain the 'limit' parameter or contrast the tool with close siblings.

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 parameter meaning. It does well for the required 'dog' parameter by explaining name or grv:/grsa: reference formats and persistence, but it completely omits the optional 'limit' parameter beyond what the bare schema constraints show.

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 that this returns one greyhound's runs from PuntersEdge results, newest first, and lists the returned fields. It distinguishes the resource from broad race or stats tools by emphasizing a single dog's form, though it does not explicitly name sibling alternatives.

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?

Usage is implied by 'One dog's runs' and by explaining accepted dog identifiers, but there is no explicit guidance about when to use this versus greyhound_stats, race_form, or horse_form. Cost and plan availability are stated, which helps, but alternatives and exclusions are absent.

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