Skip to main content
Glama

WritersLogic business agents

slot-intersect

Common free time across participants: intersect availability windows, report who blocks — Intersects up to 20 participants' free windows (up to 200 each, half-open RFC 3339 intervals with Z or offsets, so mixed time zones are fine) into the common slots at least minMinutes long, optionally clipped to a search window; when nothing fits, names the participants whose removal would create a slot. Built for an agent scheduling a meeting from already-fetched availability. It does not read ca

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": {
      "participants": "<participants>"
    },
    "name": "slot-intersect"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoOnly consider this range.
minMinutesNoMinimum slot length; default 1.
participantsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses input caps (20 participants, 200 windows), interval semantics (half-open, RFC 3339 with Z or offsets, mixed time zones accepted), the optional clipping window, and the degradation behavior of naming blocking participants when no slot fits. It stops short of stating what happens on malformed or empty availability and whether the operation is purely computational (no side effects).

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 purpose and constraints are front-loaded and dense with useful detail, but the text is truncated mid-word ('It does not read ca'), leaving a dangling clause an agent must guess at. The opening 'Common free time across participants:' duplicates the phrase that follows it.

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?

For a nested, multi-parameter computation with no output schema and no annotations, the description covers inputs, limits, and the two result modes (common slots above minMinutes, or the names of blocking participants). What is missing is the shape of the returned slots and the truncated negative statement about calendar reading.

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 coverage is 67% and the description meaningfully supplements it: 'minMinutes' is explained as a minimum slot length, 'window' as an optional clip on the search range, and participant 'free' arrays are framed as availability windows with the 200-item cap and time-zone tolerance. The 'id' field's role is only implied by 'report who blocks', which is a minor gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific verb and resource: 'intersect availability windows, report who blocks' over participants' free time. It also states the scope (common free time across participants) and the caps (20 participants, 200 windows each), which lets an agent separate it from a single-calendar tool without opening the schema.

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?

'Built for an agent scheduling a meeting from already-fetched availability' gives a real usage context and implies the tool is not a calendar reader. However, the sentence that would state the exclusion ('It does not read ca...') is cut off, and no alternative sibling is named, so the when-not-to-use guidance is incomplete.

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