Skip to main content
Glama

Coline

Share calendar

share_calendar
Idempotent

Lets a teammate or a workspace role see a calendar (free/busy or details), edit its events, or manage it.

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": {
      "workspace": "<workspace>",
      "calendarId": "<calendarId>",
      "permission": "<permission>"
    },
    "name": "share_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleIdNoEveryone with a workspace role; or give userId.
userIdNoA teammate; or give roleId.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
calendarIdYesCalendar id from list_calendars.
permissionYes

Output Schema

NameRequiredDescriptionDefault
updatedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent write (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds real value by spelling out what each access level actually confers, but it omits whether an existing grant is overwritten, whether the grantee is notified, and what authorization the caller needs.

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?

One front-loaded sentence that names the grantees first and the access levels second, with no filler. It is dense but each clause carries payload; only a minor loss for packing three access tiers into a parenthetical.

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 no explanation, and annotations cover the safety profile. For a 5-parameter mutation that grants access, though, the definition should say whether this replaces prior sharing, requires calendar ownership, and notifies the grantee.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80% and the schema already explains workspace slug provenance, calendarId from list_calendars, and the roleId/userId either-or. The description goes beyond the schema by giving meaning to the otherwise undescribed permission enum values (free_busy, view, edit, manage), which is the parameter that most affects the call.

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 the concrete effect: granting a teammate or workspace role access to a calendar, with three gradations (view free/busy or details, edit events, manage). That is a specific verb+resource. It does not distinguish itself from the obvious inverse, unshare_calendar, or explain how it differs from sibling share tools, so it stops short of a 5.

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 explicit when-to-use or when-not guidance, no mention of prerequisites such as needing owner/admin rights on the calendar, and no pointer to unshare_calendar or list_calendar_access for related operations. The agent must infer the usage context entirely from the single sentence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources