grr

Overview Schema Source Related Servers Discussions Admin

calendar.colors.get

Fetch calendar and event color definitions to map color IDs and apply consistent labels in Google Calendar via a JSON GET request.

Instructions

Returns the color definitions for calendars and events [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

Name	Required	Description	Default
`kind`	No
`event`	No
`updated`	No
`calendar`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calendar": {
+      "type": "object"
+    },
+    "event": {
+      "type": "object"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "updated": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations are provided, so the description bears the behavioral burden. It does disclose the HTTP method ([HTTP GET]) and that the response is JSON, which is useful, but it says nothing about auth, rate limits, or paging, and the body-construction boilerplate is largely irrelevant for a bodyless GET.

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 purpose is front-loaded, but the second sentence is generic request-plumbing boilerplate that applies to every tool in the family and earns little place here, diluting a one-line read operation.

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?

An output schema exists, so return values need not be described, and the description covers method and return format. However, it omits any color-specific context and the boilerplate masks rather than clarifies behavior for this specific GET tool.

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 the schema already documents all four parameters. The description restates the typed-params-vs-params-map and body_file semantics rather than adding new meaning, so baseline 3 is appropriate.

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?

The opening sentence states a specific verb and resource ('Returns the color definitions for calendars and events'), so an agent can immediately grasp what it produces. It does not differentiate against sibling tools, but there is no near-duplicate color tool among the siblings, so the lack of comparison is a minor gap.

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 guidance on when to invoke this versus alternatives like calendar.calendarList.get or calendar.events.get to obtain colors, nor any mention of prerequisites or exclusions. Usage is only implied by the resource name.

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

Deploy Server