Skip to main content
Glama

Read a calendar event

event_get
Read-onlyIdempotent

Retrieve a single calendar event by ID to inspect all current fields and get the updatedAt version token needed for subsequent edits.

Instructions

Fetch one calendar event with all its fields, including updatedAt, the version token event_update takes as expectedUpdatedAt. Use it when you have an event id and want its current state, for example before editing; use events_list to browse or find events. An id that is not in this flat fails with 404 event_not_found.

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": {
      "id": "<id>"
    },
    "name": "event_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the event, from events_list or event_create.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / id / description
      Added value: +"Id of the event, from events_list or event_create."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses that the full record is returned including updatedAt, that this token is the optimistic-concurrency input to event_update, and that a miss fails with 404 event_not_found. What it does not cover — e.g. whether the version token can be stale or how the flat scoping interacts with the id — is minor but keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the operation and return payload, then usage routing, then the failure mode. No restatement of the title and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with annotations covering the safety profile, the description supplies everything an agent needs: what comes back, why the version field matters, when to prefer the sibling, and the error outcome. Nothing material is missing.

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%, so both `id` and `wgCode` are already fully documented, including the format and source of the id. The description only adds an oblique hint about flat scoping ("not in this flat") rather than clarifying either parameter, so it sits at the baseline.

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 ("Fetch one calendar event with all its fields") and immediately scopes the result by naming the version token it carries. It distinguishes itself from events_list (browsing) and from event_update (which consumes updatedAt as expectedUpdatedAt), so an agent can place it in the workflow without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition ("when you have an event id and want its current state"), a concrete motivating scenario ("for example before editing"), and an explicit alternative ("use events_list to browse or find events"). The when/when-not split is unambiguous.

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