Skip to main content
Glama

Eventstatapp

Get an event's live status

get_event_status
Read-onlyIdempotent

Current public status of one event (GREEN go / YELLOW caution / RED stop / PENDING no update yet) with the organizer's headline and message, every race's schedule and status, and the 5 newest public updates.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe event's slug: the last part of its status page address, e.g. riverside-10k for eventstatapp.com/e/riverside-10k.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety bar is covered. Beyond that, the description adds real context: the response is limited to *public* data, the status enum is decoded inline (GREEN/YELLOW/RED/PENDING), and the update list is capped at 5 newest — behavior an agent would not otherwise know since there is no output schema.

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?

One sentence, front-loaded with the core purpose, with the status legend in parentheses where it is immediately useful. Dense but no filler; the only slight cost is that the single long sentence packs four distinct return facets together rather than scanning as a short list.

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 carries the burden of describing the return payload and does so concretely, including the status vocabulary and the 5-update cap. Minor gaps remain: nothing about behavior for an unknown or unpublished slug, and no indication of whether race-level data is empty for events without races.

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% and the slug property already carries a pattern, length bounds, and a worked example, so the description owes little here. The description only implies the parameter by saying 'one event' and adds no format or derivation guidance beyond the schema, which is the expected baseline-3 outcome.

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 names a specific resource and enumerates exactly what comes back: overall status, organizer headline/message, per-race schedule and status, and the 5 newest public updates. It is far more informative than the title alone and clearly distinct in emphasis from get_event_updates and list_events, though it never names those siblings explicitly.

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 only implied by the phrase 'current public status of one event' — an agent can infer this is the single-event lookup versus a listing tool. There is no explicit statement of when to prefer this over get_event_updates (which likely returns the full update feed), nor any note about prerequisites such as whether the event must be published to be visible.

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