Skip to main content
Glama

Read an event invite and its RSVPs

status_get_event
Read-onlyIdempotent

Read an event invite made with status_create_event: who is coming and how many people have replied (each guest's name and RSVP: confirmed for yes, maybe, pass for no, or pending), its title, details, place, date, time and theme, and whether the user has claimed it. Needs the eventId and editKey from status_create_event. Read-only.

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": {
      "eventId": "<eventId>",
      "editKey": "<editKey>"
    },
    "name": "status_get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
editKeyYeseditKey returned by status_create_event
eventIdYeseventId returned by status_create_event

Output Schema

NameRequiredDescriptionDefault
eventYesThe event as guests see it
messageYesPlain-language summary of the result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so 'Read-only' in the description is largely redundant. The genuinely additive content is the RSVP vocabulary mapping (confirmed=yes, maybe, pass=no, pending) and the fact that claim status is included, which tells the agent how to interpret values it will see. It stops short of noting authorization implications of holding an editKey or any failure behavior for stale keys.

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 and the returned field list are front-loaded in a single dense sentence with no filler or marketing language. The trailing 'Read-only.' fragment duplicates the annotations and the sentence is somewhat run-on with its parenthetical RSVP glossary, but nothing is wasted enough to impair scanning.

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 an output schema present and rich annotations, the description only needs to convey intent, prerequisites and value interpretation — all of which it does. The one omission is error behavior for an invalid or expired editKey, which matters for a credential-gated read but is a minor gap given the structured coverage.

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% and both parameters already document their provenance from status_create_event, so the description adds no new syntax or format detail. Repeating the credential requirement is mildly reinforcing but not new meaning, which lands at the baseline for a fully documented two-parameter schema.

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+resource ('Read an event invite') and immediately scopes it to the invite plus its RSVP list, enumerating exactly what is returned (guest names, RSVP states, title, details, place, date, time, theme, claim status). It also anchors the tool against its sibling by naming status_create_event as the producer of the object being read, so an agent can distinguish it from create/update without inspecting schemas.

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?

Usage context is clear: this is the retrieval counterpart to status_create_event, and it states the prerequisite credentials ('Needs the eventId and editKey from status_create_event'). It does not explicitly exclude status_update_event or say when to prefer one over the other, but the read-only framing makes the read-vs-write split implicit and unambiguous.

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