Skip to main content
Glama

Nicolas Sitter Research

list_race_explorers

Read-only

List the endurance races this site publishes results explorers for — L'Étape du Tour, the Marathon and Semi de Paris, the Triathlon de l'Alpe d'Huez, La Marmotte and their archive editions — with each one's year, sport, distance, finisher count and URL. Use this when the user asks what race data this site has, asks about results or statistics for one of these events, or wants to know how many people finished a particular edition. Returns aggregate figures per race only.

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": "list_race_explorers"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFilter to a single edition year.
sportNoFilter to "cycling", "running" or "triathlon".
clientNoOptional: identify yourself, e.g. "my-agent/1.0". Not required and never used by the tool itself — recorded only so the public tracker at /projects/agent-tools can measure how many callers self-identify when nothing forces them to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: archive editions are included in the results, and the output is limited to aggregate per-race figures rather than individual finisher records. It stops short of stating result volume or pagination, which keeps it from a 5.

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?

The core action is front-loaded in the first clause, and the returned-field list follows immediately. The event enumeration is long but earns its place by making the scope concrete and showing that archive editions count. The third sentence is a short, useful constraint rather than filler.

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 correctly compensates by listing the returned fields and clarifying that values are aggregates. All parameters are optional and schema-documented, so no param explanation is owed. Only minor gaps remain, such as whether output is paginated or how large the race list typically is.

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 100%, so all three parameters (year, sport, client) are already documented, including the sport enum values and the self-identification purpose of client. The description adds no filtering syntax or combination semantics beyond that. Baseline 3 applies when the schema carries the full burden.

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 opens with a specific verb and resource — "List the endurance races this site publishes results explorers for" — and then enumerates the actual events (L'Étape du Tour, Marathon de Paris, Triathlon de l'Alpe d'Huez, La Marmotte, plus archive editions). It also names the fields returned (year, sport, distance, finisher count, URL), so an agent knows exactly what it gets. Nothing in the sibling list overlaps this domain, so disambiguation is unnecessary.

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?

Three concrete trigger conditions are given: the user asks what race data the site has, asks about results/statistics for one of these events, or wants a finisher count for a specific edition. The closing caveat "Returns aggregate figures per race only" sets a boundary on expectations. It does not name an alternative tool for per-finisher detail, but no relevant sibling exists in this catalog.

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