Skip to main content
Glama

List calendar conflicts

list_calendar_conflicts
Read-only

«Resource busy» on a project's calendar in a window: kind 'busy' — two occurrences ('a', 'b') need one resource at times that overlap once its buffers are counted — or kind 'repair' — an occurrence ('a') needs a resource under repair — or kind 'move' — the reconfiguration before 'b' has no time to happen, because 'a' holds a unit it moves or the room it is done in while it should be done: a conflict without the two overlapping. Cancelled and paused occurrences take nothing. Any member may read.

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": {
      "project": "<project>"
    },
    "name": "list_calendar_conflicts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoWindow end, ISO 8601. Default: a week after the start; at most 400 days.
fromNoWindow start, ISO 8601. Default: yesterday.
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish this as read-only, non-destructive, and closed-world, and the description adds important domain behavior: exactly what counts as a busy, repair, or move conflict, plus the exclusion of cancelled and paused occurrences. It also states that any member may read, though it does not describe result ordering, pagination, or the returned conflict object shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is relevant and every clause appears to define a conflict kind, but the description is one dense, nested sentence with symbolic placeholders and em dashes rather than a front-loaded summary. It is readable only with effort and could be structured more clearly 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?

Given the tool's domain complexity, the description supplies the critical definitions needed to understand what conflicts are returned and who can read them. It leaves the explicit return shape and ordering unspecified, which matters more because there is no output schema, but the core semantics are covered.

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 the schema already documents project, from, to, their defaults, and the 400-day maximum. The description adds no parameter-specific syntax or meaning beyond the window concept already implied by the schema, so the baseline of 3 is appropriate.

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 identifies the resource precisely as a project's calendar conflicts within a time window, and it defines the three conflict kinds (busy, repair, move). It does not explicitly contrast this tool with list_calendar_events or list_calendar_pauses, but the scope is clear enough to select it.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool instead of the calendar event or pause list tools. The statement that cancelled and paused occurrences take nothing is behavioral context, not usage guidance, and no preconditions or alternatives are named.

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