Skip to main content
Glama

Coline

Restore calendar

restore_calendar
Idempotent

Brings back an archived calendar with its events.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
restoredYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds one meaningful behavioral detail beyond that: restored calendars bring their events back with them, so the agent knows this is a cascading restore, not just a flag flip. It does not say where the calendar is restored to, whether prior sharing/access is preserved, or what permissions are required.

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?

A single short sentence with zero filler; the resource and the key behavioral fact (events are included) are front-loaded. Nothing could be removed without losing information.

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?

For a two-parameter restore tool with full schema coverage, rich annotations, and an output schema, the description covers the essentials: what is restored and that events come with it. Gaps are minor (target location after restore, permission requirements) and not strictly necessary for correct invocation.

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%, and both parameters (workspace slug, calendarId) are fully documented in the schema with sourcing hints. The description adds no parameter-level meaning, which is acceptable at full coverage but earns only the baseline.

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?

"Brings back an archived calendar with its events" names a specific verb (restore/bring back), a specific resource (archived calendar), and the scope (events come along). It implicitly contrasts with the archive operation and is clearly distinguishable from siblings like archive_calendar or create_calendar, though no sibling is named 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 phrase "archived calendar" implies the precondition that the calendar must already be archived, which is useful context. However, there is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives (e.g., what to do if the calendar was deleted rather than archived).

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