Skip to main content
Glama

gcal_update_event

Modify an existing Google Calendar event for a connected account, changing only the fields you provide and leaving all other details unchanged.

Instructions

(Beta) Change an event of a Google Calendar of a connected Google account: only the fields given change (at...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses PATCH-style partial-update semantics and a beta status, which is genuinely useful, but says nothing about required permissions/OAuth scopes, reversibility, what happens to fields omitted, or what the response contains — and its final clause is cut off.

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 text is short with no padding, but it is truncated rather than concise, so the trailing fragment '(at...' adds no information. It is front-loaded correctly with the beta marker and the verb+resource.

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?

For a mutation tool with no annotations, no output schema, and an empty parameter schema, the description should explain targeting, permissions, and side effects. Instead it is truncated and leaves the agent without enough to invoke it confidently.

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?

The input schema declares zero properties, so there are technically no parameters to document and the baseline would be 4. But for an update tool an empty schema is itself a significant gap, and the description does not explain how the caller specifies the event to change or the fields to set — leaving the calling convention unexplained.

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 names a specific verb and resource ('Change an event of a Google Calendar'), which separates it from the create/delete siblings. However, it is truncated mid-sentence at '(at...', so the scope of the change is never finished and the description gives no hint about how a target event is identified.

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 when-to-use guidance and no reference to alternatives such as update_calendar_event, which appears to overlap directly. The only actionable hint is 'only the fields given change,' which describes partial-update behavior rather than when to choose this tool.

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