Skip to main content
Glama

Coline

List events

list_events
Read-onlyIdempotent

Lists the person's schedule across all their Coline calendars between two times (up to 93 days).

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>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesISO 8601 with a time zone offset, e.g. 2026-11-20T15:00:00-08:00.
startYesISO 8601 with a time zone offset, e.g. 2026-11-20T15:00:00-08:00.
calendarsNomine (default): the person's own schedule in every workspace. workspace: everything on this workspace's calendars they can see.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them by disclosing the hard 93-day window limit and that results span all calendars rather than one. It stops short of discussing result ordering or truncation behavior.

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 that front-loads the resource and scope with zero filler. Every clause (all calendars, two times, 93-day cap) carries 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?

With an output schema present, return values need not be explained, and annotations cover the read-only safety profile. The description supplies the key constraint an agent could otherwise trip over (the 93-day maximum) and the calendar scope, leaving only minor gaps like event ordering or overlap semantics.

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%, with each of the four parameters documented including the mine/workspace enum and the ISO 8601 offset format. The description adds only the vocabulary "two times" for start/end, which the schema already explains in more detail, so baseline 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 names a specific verb ("Lists") and resource ("the person's schedule across all their Coline calendars") plus a time-range scope, so an agent knows exactly what it returns. It does not distinguish itself from plausible siblings such as search_events or alert_events_list, which keeps it below 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 Guidelines3/5

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

Usage is implied by the "between two times" framing and the 93-day ceiling, which tells the agent the tool is for bounded time-window retrieval. There is no explicit statement of when to prefer an alternative tool or when this tool is the wrong choice.

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