Skip to main content
Glama
Sign In
gcal-mcp

gcal-mcp

by spokoistvie-cyber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_events

List Google Calendar events for a date range in time order, filtered by text, color, calendar, or missing color, with IDs and recurrence IDs.

Instructions

События за период по возрастанию времени. Показывает цвет и ID; у повторяющихся — recurringEventId серии.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoПоиск по тексту события.
colorIdNoЦвет, строка "1"–"11": 1 лаванда, 2 шалфей (зелёный), 3 виноград (сиреневый), 4 фламинго (коралловый), 5 банан (жёлтый), 6 мандарин (оранжевый), 7 павлин (бирюза), 8 графит (серый), 9 черника (синий), 10 базилик (тёмно-зелёный), 11 томат (красный).
timeMaxNoКонец периода, ISO. По умолчанию — +7 дней.
timeMinNoНачало периода, ISO. По умолчанию — сейчас.
calendarIdNoID календаря. "primary" — основной, "all" — сразу все календари аккаунта.
maxResultsNoСколько событий вернуть, по умолчанию 50 (для "all" — на календарь).
onlyNoColorNoТолько события без цвета — перед покраской.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the entire behavioral burden. It does disclose ordering and returned fields (color, ID, recurringEventId), but says nothing about read-only semantics, auth/scope requirements, pagination beyond maxResults, or result limits — a substantial gap for a 7-parameter query tool.

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?

Two compact sentences, front-loaded with the core purpose and then the return-shape detail. It is telegraphic and fragment-like but has no padding or redundancy.

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?

With 7 optional parameters, no output schema, and no annotations, the definition should say more about result shape and boundaries. It covers ordering and a few returned fields, which is minimum viable, but leaves routing versus siblings and behavioral constraints unaddressed.

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%, including the full colorId enum legend and defaults for timeMin/timeMax/maxResults, so the schema does the heavy lifting. The description only alludes to 'период' and 'цвет' without adding format or interaction detail; 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 specific action and resource: events for a period, returned in ascending time order, with color/ID and recurringEventId for series. That is concrete enough to distinguish it from list_calendars, though it never names a sibling explicitly.

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 'События за период' and by schema hints such as onlyNoColor ('перед покраской'), but there is no explicit statement of when to use this versus color_events or create_event, and no prerequisites or exclusions.

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