Skip to main content
Glama

Coline

Get event

get_event
Read-onlyIdempotent

Reads one event in full: description, attendees and their responses, and the join link.

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

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent id from list_events.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
endYes
urlYes
startYes
titleYes
allDayYes
eventIdYes
joinUrlYes
locationYes
timeZoneYes
attendeesYes
organizerYes
myResponseYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description adds the field scope of the read, which is mild extra context, but it does not cover edge cases such as an event lacking a join link or attendee lists being empty.

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?

A single front-loaded sentence with no filler; the scope and returned content are stated before anything else, and every clause carries information.

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?

For a simple two-required-parameter read tool with full annotation coverage, a complete parameter schema and an output schema, this is nearly complete. Only minor behavioral caveats (missing join link, pagination-free attendee list assumptions) are unstated.

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 are documented in-schema (including the workspace slug example and the origin of eventId). The description adds no meaning beyond that, so the baseline 3 applies.

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?

"Reads one event in full" gives a specific verb and single-resource scope, and the enumeration of returned fields (description, attendees and responses, join link) makes the purpose concrete. It implicitly contrasts with the plural listing siblings (list_events), but never names an alternative 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: the agent must infer that this is the tool for fetching a single event's details once its id is known (the schema's "Event id from list_events" supplies that link). There is no explicit when-to-use versus get_event_reminders or respond_to_event, and no stated preconditions.

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