Skip to main content
Glama
navig-run

NAVIG

Official
by navig-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Change Google Calendar

connector_google_calendar_act
Destructive

Create, update, delete, or move Google Calendar events. Pass resource_id and params; returns success with resource or failure reason.

Instructions

Change data in Google Calendar: reply, create, update, delete, archive, label, send or move — whichever this provider supports. Pass resource_id for an existing item and params for the payload; returns success plus the affected resource, or success: false with the reason. An unsupported action is refused, never silently applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoAction-specific payload, e.g. {to, subject, body} for send, {body} for reply, {add_labels, remove_labels} for label
action_typeYesWrite to perform. The provider must support it — a value outside its supported set is refused with success: false, not silently applied.
resource_idNoNative id of the item to change, when the action targets an existing item (reply, update, delete, archive, label, move). Omit it for create/send.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • changedInput schema / properties / action_type / description
      Previous value: -"Action to perform. Allowed values: reply, create, update, delete, archive, label, send, move"New value: +"Write to perform. The provider must support it — a value outside its supported set is refused with success: false, not silently applied."
    • addedInput schema / properties / action_type / enum
      Added value: +[
+  "reply",
+  "create",
+  "update",
+  "delete",
+  "archive",
+  "label",
+  "send",
+  "move"
+]
    • changedInput schema / properties / params / description
      Previous value: -"Action-specific parameters (e.g. body, subject, labels)"New value: +"Action-specific payload, e.g. {to, subject, body} for send, {body} for reply, {add_labels, remove_labels} for label"
    • changedInput schema / properties / resource_id / description
      Previous value: -"ID of the resource to act on (if applicable)"New value: +"Native id of the item to change, when the action targets an existing item (reply, update, delete, archive, label, move). Omit it for create/send."
    • addedInput schema / properties / resource_id / minLength
      Added value: +1
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description nonetheless adds real behavioral value beyond them: the return contract ('success plus the affected resource, or success: false with the reason') and the refusal semantics ('never silently applied'). It omits auth/permission requirements and whether deletes are reversible, which is why it stops short of 5.

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 tight sentences, front-loaded with the action inventory before the invocation and return contract. Every clause carries information, though the long action enumeration is partly redundant with the enum in the schema.

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

Completeness4/5

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

With no output schema, the description compensates by describing the success/failure return shape, and it clarifies payload structure and the refuse-unsupported-action contract. Destructive and open-world behavior is covered by annotations. Adequate for a multi-action mutation tool, though auth prerequisites remain unstated.

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%, so the schema already documents action_type, resource_id and params thoroughly, including the resource_id omission rule and enum semantics. The description repeats the resource_id/params mapping without adding syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 description states a clear verb+resource ('Change data in Google Calendar') and enumerates the eight supported actions, so an agent can tell this is the write counterpart to connector_google_calendar_search and connector_google_calendar_fetch. It does not explicitly name those siblings, but the name/title already anchor the resource. Minor deduction for the action list mixing non-calendar verbs (reply, label, send) that could momentarily confuse the domain.

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?

It explains how to invoke ('Pass resource_id for an existing item and params for the payload'), which is somewhat usage-oriented, but never states when to choose this tool over connector_google_calendar_fetch/search or when an action is appropriate. 'Whichever this provider supports' hints at provider scoping without telling the agent how to know what is supported. Usage is implied rather than explicit.

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