Skip to main content
Glama

get_marathon

Retrieve detailed marathon information including countdown timers and structured Schema.org data for specific race events.

Instructions

Get detailed information about a specific marathon including countdown and Schema.org data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMarathon ID, e.g. "tokyo2026", "boston2026", "berlin2026"

Implementation Reference

  • The `get_marathon` tool fetches detailed marathon information from the RunDida API and formats it into a text response with event details, weather, and course info.
    server.tool(
      'get_marathon',
      'Get detailed information about a specific marathon including countdown and Schema.org data',
      { id: z.string().describe('Marathon ID, e.g. "tokyo2026", "boston2026", "berlin2026"') },
      async ({ id }) => {
        const data = await fetchJSON(`${BASE_URL}/api/marathons/${id}.json`);
        const m = data.marathon;
        const raceDate = new Date(m.date);
        const now = new Date();
        const daysUntil = Math.ceil((raceDate - now) / (1000 * 60 * 60 * 24));
        let text = `## ${m.name.en}\n\nDate: ${m.date}\nCity: ${m.city}\n`;
        if (m.country) text += `Country/Region: ${m.country}\n`;
        text += `Timezone: ${m.timezone}\n`;
        text += `Days until race: ${daysUntil > 0 ? daysUntil : 'Race has passed'}\n`;
        if (m.weather) {
          text += `\n### Race Day Weather\nTemperature: ${m.weather.avgTempC}°C / ${m.weather.avgTempF}°F\n`;
          text += `Humidity: ${m.weather.humidity}% | Wind: ${m.weather.windKmh} km/h | Rain: ${m.weather.precipPct}%\n`;
          text += `Conditions: ${m.weather.conditions}\n`;
        }
        if (m.course) {
          text += `\n### Course Profile\nType: ${m.course.type} | Elevation: ${m.course.elevationGain}m | Terrain: ${m.course.terrain}\n`;
          text += `${m.course.profile}\n`;
        }
        text += `\nPage: ${m.links.page}\nCountdown: ${m.links.countdown}\n`;
        return { content: [{ type: 'text', text }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but does not specify whether it requires authentication, has rate limits, or details about the response format (e.g., structure of Schema.org data). This leaves gaps in understanding the tool's behavior beyond basic retrieval.

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 description is a single, efficient sentence that front-loads the core purpose without unnecessary details. It could be slightly improved by structuring information more explicitly, but it avoids redundancy and wastes no words, making it appropriately concise for the tool's simplicity.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and data types retrieved, but lacks details on behavioral aspects like authentication or response format, which are important for a tool with no annotations to guide the agent fully.

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?

The input schema has 100% description coverage, with the 'id' parameter clearly documented as a Marathon ID with examples. The description adds minimal value beyond this, mentioning 'a specific marathon' which aligns with the schema but does not provide additional semantic context or usage examples. This meets the baseline for high schema coverage.

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 tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific marathon'), including what information is retrieved ('countdown and Schema.org data'). However, it does not explicitly differentiate from sibling tools like 'marathon_countdown' or 'list_marathons', which might offer overlapping or related functionality.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or comparisons to sibling tools such as 'list_marathons' for listing multiple marathons or 'marathon_countdown' for countdown-specific data, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/XWeaponX7/rundida-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server