Skip to main content
Glama

Eventstatapp

Get an event's update history

get_event_updates
Read-onlyIdempotent

The public announcements an event's organizer has posted, newest first (up to 50).

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_updates"
  }
}

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.
limitNoMost updates to return, newest first (1–50, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely new behavior: 'public' visibility, newest-first ordering, and a hard ceiling of 50. It does not say what happens on an invalid or unknown slug, or how to page past the cap.

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 fragment with zero filler; ordering and cap are packed into one clause. It is appropriately sized, though it reads as a noun phrase rather than a directive, which slightly weakens scannability.

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?

The tool is simple (one required param, no nesting, fully documented schema) and the annotations carry the safety profile, so little is required. However, with no output schema, the description never indicates what an 'update' contains (e.g. title, body, timestamp), leaving the return shape undisclosed.

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 the schema already documents both slug and limit, including the format example and the 1-50 range. The description's 'newest first (up to 50)' only restates the limit constraint and adds no meaning beyond the schema.

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?

Names a specific resource and its sub-resource ('the public announcements an event's organizer has posted'), which is clearly distinct from get_event_status and list_events. It omits an explicit verb (e.g. 'Retrieve'), but the noun phrase is precise enough for an agent to know what it returns.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the sibling tools or how this differs from reading an event's status. The only signal is implicit: an agent must infer that this fetches announcements rather than the event's current status.

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