Skip to main content
Glama
Sign In

AccountHub

by ai.accounthub
OverviewDiscussionsAdmin

get_event

Read-only

Fetch one Google Calendar event by id (from list_calendar_events or search results, its event_id + account fields). Pass account when more than one calendar-capable account is connected. Check status: Google can return a cancelled event here even though list_calendar_events omits it; response_status is the attendee reply, not the event lifecycle. Recurring instances include recurring_event_id and original_start_time.

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

Input Schema

NameRequiredDescriptionDefault
accountNoAccount label the event belongs to (see list_accounts). Required when several calendar-capable accounts are connected.
event_idYesEvent id (from list_calendar_events, its `event_id` field).
calendar_idNoCalendar id (default 'primary').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With readOnlyHint already declaring the safety profile, the description adds genuinely useful behavioral detail: status may be cancelled even though list_calendar_events omits such events, and response_status is the attendee reply rather than the event lifecycle. It also notes recurring-instance fields, which helps the agent interpret the response correctly.

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?

The description is front-loaded with the core action and id source, then adds the account condition and response caveats. Every sentence carries useful information without unnecessary length.

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 read-only single-event fetch with a fully documented input schema and no output schema, the description supplies the key completeness details: how to identify the event, when account is needed, and how to interpret status and recurring fields.

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 all three parameters already have documented semantics. The description mostly repeats the account condition and event_id source, without adding much beyond the schema or clarifying calendar_id behavior.

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?

The description gives a specific verb and resource: 'Fetch one Google Calendar event by id.' It also names where the id comes from (list_calendar_events or search results), which clearly distinguishes it from the listing sibling.

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?

It states the primary use case and the condition for passing account when multiple calendar-capable accounts are connected. It does not explicitly say when not to use it or name the listing alternative as a separate route, but the source hint makes the intended usage clear.

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

All AccountHub 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