Skip to main content
Glama

color_events

Assign Google Calendar colors to multiple events in one call and return a report of colored events and any errors.

Instructions

Покрасить много событий одним вызовом. Возвращает отчёт: сколько покрашено и где ошибки.

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": {
      "ids": "<ids>",
      "colorId": "<colorId>"
    },
    "name": "color_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesID событий из list_events.
scopeNoЧто менять у повторяющегося: instance — только этот раз (по умолчанию), series — всю серию, following — этот и все следующие.
colorIdYesЦвет, строка "1"–"11": 1 лаванда, 2 шалфей (зелёный), 3 виноград (сиреневый), 4 фламинго (коралловый), 5 банан (жёлтый), 6 мандарин (оранжевый), 7 павлин (бирюза), 8 графит (серый), 9 черника (синий), 10 базилик (тёмно-зелёный), 11 томат (красный).
calendarIdNoID календаря. "primary" — основной, "all" — сразу все календари аккаунта.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the call returns a report with a success count and error locations, which implies partial-failure tolerance, but it says nothing about required permissions, whether existing colors are overwritten, batch limits, or whether the operation is atomic.

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 short sentences with zero waste, front-loading the action and then the return shape. Every clause earns its place.

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 four parameters, full schema coverage, and no output schema, the description covers the essentials by stating the return report shape. However, for an unannotated batch mutation it omits failure semantics (does one bad ID abort the rest?), permissions, and scale limits.

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% and enums for scope and colorId are fully documented in the schema, so the baseline of 3 applies. The description adds no parameter meaning beyond what the schema already states.

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?

Description states a specific verb+resource with batch scope: "Покрасить много событий одним вызовом" (paint many events in one call). The bulk scope implicitly distinguishes it from the single-event update_event sibling, though it never names the 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?

The 'many events in one call' framing implies when the tool is appropriate (bulk color changes), but there is no explicit guidance on when to prefer update_event instead, no prerequisites, and no batch-size limits or exclusions.

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