Skip to main content
Glama
Sign In

Exogram — Personal AI Agent & Workspace

by io.github.Richard-Ewing
OverviewDiscussionsAdmin

calendar_list_events

List upcoming meetings, agenda items, and schedule availability from Google Calendar (read-only).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calendar_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch query or event keyword (e.g., "xAI sync", "Migration", "Team standup").
max_resultsNoMaximum number of events to return (1-20, default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it does contribute the useful "read-only" guarantee. Beyond that it is thin: it does not say which calendar is queried, how "upcoming" is windowed, whether recurring events are expanded, or what fields come back — and the "schedule availability" claim implies free/busy behavior the tool does not appear to have.

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

Conciseness4/5

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

One front-loaded sentence with the resource, the qualifier "upcoming," and the read-only property — no padding. It loses a point because the enumeration "agenda items, and schedule availability" adds words that are not backed by the implementation.

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

Completeness3/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 full schema coverage and no output schema, the essentials are roughly present, and the read-only note covers safety. Gaps remain around the "upcoming" time window (no time-range parameter exists, so the default is unexplained) and the over-promise of availability data.

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% (query, max_results, both with examples and defaults), so the baseline is 3. The description adds nothing further — notably it never mentions keyword search, so the agent must read the schema to learn the tool filters by query.

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?

"List upcoming meetings ... from Google Calendar" gives a specific verb plus resource, and "(read-only)" implicitly separates it from the sibling calendar_create_meeting. However, "agenda items" and "schedule availability" are not things the two-parameter schema can express, so the stated scope is broader than the actual capability.

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

Usage Guidelines2/5

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

There is no statement of when to prefer this tool, when not to, or what the alternative is (create_meeting is the only calendar sibling, but nothing routes between them). "Upcoming" implies a recency use case but no prerequisite or trigger is spelled out.

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

All Exogram — Personal AI Agent & Workspace 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