Skip to main content
Glama

get_event

Read-only

Read one calendar event in full: description, location, video call link, organizer and every attendee with their answer. Needs an eventId from search_events or get_schedule-style listings.

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>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYes

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=true and destructiveHint=false, so the safety profile is covered. The description adds the key behavioral fact that results are exhaustive rather than summarized (all attendees with responses), but says nothing about permissions, error behavior for a bad eventId, or visibility of private events.

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?

Two tight sentences with the payload of returned fields front-loaded and the prerequisite second. No filler; the only mild density issue is the long comma-separated field list, which is nonetheless informative.

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 carries the return-value burden and discharges it by naming the fields returned, including attendee responses. For a one-parameter read tool with annotations covering safety, the remaining gap is only failure/permission behavior, which is minor.

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 0% for the single eventId parameter, so the description must compensate. It does add genuine meaning by specifying the provenance of the ID (from search_events or schedule listings), but gives no hint about the ID's format or validation beyond the schema's minLength constraint.

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?

States a specific verb and resource ('Read one calendar event in full') and then enumerates exactly what 'full' means: description, location, video call link, organizer, and every attendee with their answer. An agent can immediately tell this is a single-event detail fetch rather than a listing or search.

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?

Explicitly states the prerequisite ('Needs an eventId from search_events or get_schedule-style listings'), which routes the agent through the correct sibling first. It stops short of saying when to prefer this over get_schedule or what to do if the event is not found, so it is strong context without full when/when-not coverage.

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