Skip to main content
Glama

Horse Truth Machine Intelligence

by au.com.horsetruth
OverviewDiscussionsAdmin

horse_signal

Read-only

PAID: US$0.02 per successful autonomous x402 call, or 1 Horse Truth direct credit. Return one named derived Horse Truth signal for a horse, such as readiness, biomechanics, progression, trouble watch, class, reliability, alerts or winning conditions. signal=race_day_signals returns every race-day signal Horse Truth measured for the horse (ran better than its finish, beat the day's track pattern, running profile, form turning point). Use this tool when you need one named signal only (for example readiness or class_rating). Use horse_snapshot instead for several signals at once, and horse_intelligence for everything. signal=stride_measures returns the horse's stride measures from race tracking data: held its stride late, lifted its stride rate late, stride against its own runs and stride type.

Input Schema

NameRequiredDescriptionDefault
horseYesHorse name as printed in an Australian form guide, e.g. 'Chance With Wolves'. Case and country suffixes like (NZ) are ignored. If unsure of the exact name, call resolve_horse first.
signalYesWhich single signal to return. One of the listed values, e.g. 'readiness'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / signal / enum
      Previous value: -[
-  "condition",
-  "readiness",
-  "closing_profile",
-  "closing_par",
-  "progression",
-  "forward_setup",
-  "trouble_watch",
-  "class_rating",
-  "biomechanics",
-  "winning_conditions",
-  "horse_type",
-  "reliability",
-  "distance_signature",
-  "headline",
-  "alerts",
-  "attention_score"
-]New value: +[
+  "condition",
+  "readiness",
+  "closing_profile",
+  "closing_par",
+  "progression",
+  "forward_setup",
+  "trouble_watch",
+  "class_rating",
+  "biomechanics",
+  "winning_conditions",
+  "horse_type",
+  "reliability",
+  "distance_signature",
+  "headline",
+  "alerts",
+  "attention_score",
+  "race_day_signals",
+  "stride_measures"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / signal / description
      Previous value: -"Which single signal to return. One of the listed values."New value: +"Which single signal to return. One of the listed values, e.g. 'readiness'."
  3. Changed2 schema fields changed
    • addedInput schema / properties / horse / description
      Added value: +"Horse name as printed in an Australian form guide, e.g. 'Chance With Wolves'. Case and country suffixes like (NZ) are ignored. If unsure of the exact name, call resolve_horse first."
    • addedInput schema / properties / signal / description
      Added value: +"Which single signal to return. One of the listed values."
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds genuinely new behavioral context: the per-call cost (US$0.02 per successful x402 call or 1 Horse Truth credit) and the fact that billing is on success, which matters for agent budgeting. It does not mention auth requirements, rate limits, or failure behavior when a signal is unavailable for a horse.

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?

Pricing is front-loaded, followed by purpose, signal enumeration, and routing guidance — a sensible order with no filler. There is mild redundancy in listing 'readiness' and 'class' twice across the enumeration and the usage example, which keeps it from a 5.

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 no output schema, the description partially carries the return-value burden by describing what race_day_signals and stride_measures yield. For a two-parameter lookup tool with full schema coverage and clear annotations, that is nearly sufficient; the shape of a generic signal response and what happens when a signal is missing for a horse are the remaining gaps.

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 100%, so the baseline is 3, but the description goes further by giving semantic meaning to enum values the schema leaves bare: race_day_signals is unpacked into four measured components and stride_measures into four stride metrics, and several other signal names are illustrated. The remaining 14 enum values are still only names, so it falls short of full compensation.

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 names a specific verb and resource (return one named derived Horse Truth signal for a horse) and enumerates the signal families it can produce. It explicitly distinguishes itself from horse_snapshot (several signals) and horse_intelligence (everything), so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

It states the selection condition directly ('use this tool when you need one named signal only') and names both alternatives with the condition that selects each. It also clarifies the special enum values race_day_signals and stride_measures as within-scope calls rather than separate tools.

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

All Horse Truth Machine Intelligence 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