Skip to main content
Glama

QDev

Get an event as a calendar file

get_event_calendar
Read-onlyIdempotent

One event as an iCalendar (.ics) file, ready to add to a calendar. Returns the file's name, media type and text.

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": "get_event_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe event's id, from list_events or search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 covered, and the description adds genuinely new information about the response shape (file name, media type, text) in the absence of an output schema. It does not mention failure behavior when the id is unknown, which keeps it from 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?

Two short, front-loaded sentences with no filler: the first states what the tool produces and its purpose, the second enumerates the return fields. Every sentence earns its place.

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 one-parameter read that returns a single artifact, the description covers purpose, format and return contents, and the annotations cover safety and idempotency. The only gap is what happens when the event id does not exist.

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 the single 'id' parameter is already documented in the schema, including where to source it ('from list_events or search'). The description adds no further meaning about the id, 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?

States a concrete verb and resource ('One event as an iCalendar (.ics) file') and identifies the output format, which implicitly separates it from the JSON-oriented get_event sibling. It stops short of naming an alternative explicitly, so it lands just below the top band.

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 by the format ('ready to add to a calendar') – an agent can infer you call this when a downloadable/importable calendar file is wanted rather than structured event data. There is no explicit when/when-not guidance and no named alternative such as get_event.

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