Skip to main content
Glama
Sign In
gg-mcp

gg-mcp

by tannht
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_calendar_events

Retrieve upcoming calendar events with configurable max results and lookback period. Filter by days back to focus on recent or future events.

Instructions

List events. Timezone: Asia/Ho_Chi_Minh.

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

Input Schema

NameRequiredDescriptionDefault
max_resultsNo
days_backNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, so the description must convey behavioral traits. It only mentions a timezone, but does not disclose that this is a read-only operation, the effect of days_back (e.g., how far to look back), or that max_results caps the returned events. Critical safety and behavior information is missing.

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

Conciseness3/5

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

The description is very brief (two sentences), which is concise but at the expense of necessary information. It is front-loaded with the core action, but the timezone statement could be better integrated or omitted if default.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and only two parameters, the description should cover basic behavior: what events are listed (primary calendar?), how days_back interacts with current time, and the effect of max_results. The timezone alone is insufficient for complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning parameters have no descriptions in the schema. The tool description adds no information about the parameters 'max_results' or 'days_back', leaving the agent to infer their meaning from names and defaults alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'List events' which is a verb+resource, but lacks specificity about calendar context. It is clear but not detailed enough to distinguish from hypothetical other event-listing tools. Given sibling tools include only one calendar-related list, it suffices minimally.

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?

No guidance on when to use this tool versus alternatives, no mention of default calendar or time range behavior. The description does not help with selection criteria.

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

Deploy Server

Other Tools