Skip to main content
Glama

Coline

Check availability

check_availability
Read-onlyIdempotent

Shows whether the person and the teammates given are free between two times, with what's in the way.

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>",
      "startsAt": "<startsAt>",
      "endsAt": "<endsAt>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
endsAtYesISO 8601 with a time zone offset.
startsAtYesISO 8601 with a time zone offset.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
excludeEventIdNoIgnore this event, e.g. the one being moved.
attendeeUserIdsNoTeammates by user id, from find_people.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so safety is fully covered. The description adds one piece of real behavior beyond that — it returns the blocking items, not just a boolean. However, it says nothing about whether teammate calendars require sharing permissions or about visibility limits, which is the main behavioral unknown for a cross-person availability check.

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

Conciseness4/5

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

One front-loaded sentence with no filler, and the 'what's in the way' clause is a useful, compact hint about output content. Minor ambiguity in 'the person' (presumably the authenticated user or a single implicit subject) keeps it from being fully tight.

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?

Return values need not be explained because an output schema exists, and the annotation block covers the safety profile. What remains thin is operational context: whether the caller's own calendar is included, what happens when a teammate's calendar is unavailable, and how this relates to booking or proposing-time siblings.

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%, so every parameter is already documented (including the find_people provenance for attendeeUserIds and the workspace-slug hint). The description only restates 'person and teammates' and 'between two times', adding no semantics beyond the schema — baseline 3 applies. It notably does not explain the excludeEventId use case, though the schema does.

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 operation: determine whether the caller and the named teammates are free in a given time window, plus the conflicting items ('what's in the way'). That is concrete enough to distinguish it from scheduling or booking tools in the sibling list. It falls short of 5 only because no sibling is named as the contrasting alternative.

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 rather than stated: an agent can infer this is the pre-scheduling free/busy probe, especially from 'what's in the way'. There is no explicit when-to-use condition, no when-not, and no pointer to alternatives such as booking or proposing times.

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