Skip to main content
Glama

Coline

Show calendar set

show_calendar_set
Idempotent

Shows exactly the calendars in a set and hides the rest.

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

Input Schema

NameRequiredDescriptionDefault
setIdYesCalendar set id from list_calendar_sets.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations declare readOnlyHint=false while the tool is named "show," which could confuse an agent; the description resolves this by disclosing that the operation actually changes visibility and hides calendars outside the set. That is real value beyond the structured hints. It still does not say whether the hiding is per-user or global, or how to undo it, which keeps it below 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?

A single sentence with no filler, front-loading the primary effect and immediately qualifying it with the side effect. Nothing is redundant or buried.

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 and parameters are fully documented, so the description need not explain return values. However, for a non-read-only, visibility-changing tool, the description leaves out scope and reversibility (per-user vs. shared view state, how to restore hidden calendars), which an agent would want before invoking it.

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 are documented in the schema with their sources (setId from list_calendar_sets, workspace slug from workspaces.list). The description adds no additional meaning about either parameter, 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 states a specific verb and resource ("Shows exactly the calendars in a set") and adds the contrasting effect ("hides the rest"), which separates it from show_calendar, which presumably displays a single calendar. It stops short of naming any sibling explicitly, so the differentiation is inferential rather than stated.

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?

Usage is only implied: an agent can infer this is the tool to view a calendar set, but there is no explicit guidance on when to prefer it over show_calendar or list_calendar_sets, and no stated preconditions. The only strong cue is the schema note that setId comes from list_calendar_sets, which is in the schema rather than the description.

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