Skip to main content
Glama

Coline

Archive calendar

archive_calendar
DestructiveIdempotent

Archives a calendar and hides its events. It can be restored.

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>"
    },
    "name": "archive_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
calendarIdYesCalendar id from list_calendars.

Output Schema

NameRequiredDescriptionDefault
archivedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description still earns credit for adding behavior beyond those flags: the calendar's events are hidden as a side effect, and the operation is reversible. It does not say who can restore or whether shared users lose access, which keeps it from a 5.

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 the primary action and side effect front-loaded, then the reversibility qualifier. Nothing is redundant or padded.

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 a full input schema, an output schema and rich annotations, the description only needs to supply the human-relevant consequences, and it does partially (events hidden, restorable). It stops short of stating what restore path is used or what happens to sharing/access, which matters for a destructive-flagged 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%: workspace is documented with its source (workspaces.list) and calendarId with its source (list_calendars). The description adds no further parameter meaning, so the baseline of 3 applies.

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 pairs a specific verb ("Archives") with a specific resource ("a calendar") and discloses the side effect that its events are hidden. It also implicitly distinguishes archive from a hard delete by noting it "can be restored," though it does not name any sibling tool 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 reversibility note implies the main selection logic (prefer this over a permanent delete when the change may need undoing), but the agent must infer that. There is no explicit when-to-use statement and no naming of alternatives such as restore_calendar or delete-style tools.

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