Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__calendar_get_event

Read-only

Get details of a specific calendar event by its event ID. Returns the full event (all attendees, reminders, conference data), with the description converted to plain text; use full for the original (often HTML) description.

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": {
      "event_id": "<event_id>"
    },
    "name": "gws-mcp__calendar_get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoKeep the description exactly as stored (often multi-KB HTML from Zoom/scheduling tools) instead of converting it to plain text.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
event_idYesThe calendar event ID
calendar_idNoCalendar ID (default: "primary")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true already signals a safe read, so the description's added value is in disclosing return content: full event with all attendees, reminders and conference data, and that the description field is converted to plain text unless `full` is set. That is real behavioral context an agent could not infer from annotations; the only gap is no mention of failure behavior for invalid or inaccessible event IDs and no pagination/size caveats.

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 compact sentences, front-loaded with what the tool does and its key parameter, then the non-default `full` behavior. Nothing is redundant with the name and no filler appears.

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 usefully takes on the return-shape burden by enumerating attendees, reminders, conference data, and the plain-text conversion. It is near-complete for a simple get-by-ID read, missing only guidance on obtaining an event ID or handling an event that isn't found.

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% and the schema already documents `full` (including the multi-KB HTML note), `account`, and the `calendar_id` default of "primary". The description restates the `full` behavior rather than adding syntax, format, or constraint detail beyond the schema, so baseline 3 is correct.

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 ("Get details of a specific calendar event") plus the identifying key ("by its event ID"), which cleanly distinguishes it from the sibling list-style tool gws-mcp__calendar_list_events without needing the schema opened.

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 implied by "by its event ID" — an agent knows it must already have an ID — but the description never names an alternative (e.g., calendar_list_events to obtain IDs) or states exclusions. The "use full for the original description" clause is parameter-level guidance rather than when-to-use-this-tool guidance.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources