Skip to main content
Glama

SportStatsAPI

Find horses

find_horses
Read-only

Find horses, jockeys and trainers by name, with their ids (for get_runner_form), most recently seen first.

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

Input Schema

NameRequiredDescriptionDefault
nameYespart of a horse, jockey or trainer name (2-64 characters)
limitNomax results per kind (default 20, max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so safety is covered. The description adds genuine behavior beyond that: ordering is 'most recently seen first' and results include ids. It does not explain why a read tool is marked non-idempotent, whether matching is case-insensitive, or how the three entity kinds are combined in the response.

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?

A single front-loaded sentence carrying purpose, entity kinds, returned ids, the chaining target, and sort order with no filler. Only nit is that the ordering clause is tacked on at the end rather than stated up front.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter lookup with no output schema, the description covers the essentials (entity kinds, ids returned, sort order). It leaves out the response shape beyond ids, whether names are echoed, substring/case matching semantics, and no-match behavior, which matter for a discovery tool feeding get_runner_form.

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 coverage is 100%: both 'name' (2-64 chars, part of a name) and 'limit' (per kind, default 20, max 50) are fully documented. The description only restates that the name can match a horse, jockey or trainer, adding no format or matching detail beyond the schema; baseline 3 applies.

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 specific verb and resource set: find horses, jockeys or trainers by name, and explicitly says ids are returned for chaining into get_runner_form. This distinguishes it well from the get_* detail tools, though the primary entity is ambiguous (the name is find_horses but it also covers jockeys and trainers).

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?

The parenthetical '(for get_runner_form)' gives a concrete downstream use case, which is real routing guidance. However, it never states when NOT to use it (e.g. vs get_race or get_racing_stats), and there is no guidance on resolving multiple matches or what to do when nothing is found.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources