Skip to main content
Glama

Coline

Show calendar

show_calendar
Read-onlyIdempotent

Shows the person's week inside the chat, where they can see their schedule, open events and drag them to new times. Use it when they want to look at their calendar or find a time.

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

Input Schema

NameRequiredDescriptionDefault
dateNoA day in the week to show; default this week.
eventIdNoOpen this event.
timeZoneNoThe person's time zone, for which days the week holds.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
eventsYes
openEventYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the result renders inside the chat as an interactive week view where events can be opened and dragged to new times, meaning invocation has a UI side effect rather than returning plain data. It says nothing about permissions, what the default view is, or what happens on the server when a dragged event moves, which is a real gap for a tool with implicit follow-on mutation.

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, front-loaded with what the tool shows before the usage trigger. No wasted clauses and no restatement of the title.

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?

Output schema exists, so return values need no explanation, and all four parameters are documented in the schema. The description covers the rendering model and the primary use case; the only shortfall is the absence of default behavior (this week) and any mention that workspace is mandatory, though the schema flags the latter.

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 description coverage is 100%, so the baseline is 3, but the description does clarify the core semantics: the tool renders a *week*, anchored on a given day, which explains why date and timeZone exist and how they interact ('which days the week holds'). It still adds nothing about eventId (deep-linking to a single event) or about the workspace requirement.

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?

States a specific verb and resource: it 'Shows the person's week inside the chat,' and even describes the rendered interaction (view schedule, open events, drag to new times). It does not, however, distinguish this from near-name siblings like show_calendar_set or the other show_* tools, so the agent gets no sibling differentiation from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-use context: 'Use it when they want to look at their calendar or find a time.' That is enough to route an intent, but there are no exclusions or named alternatives (for example, when to prefer the raw settings or calendar-set 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