OrgLines

Planner: Suggest slots

planner_suggest_slots

Read-only

Suggest the earliest meeting slots when the caller and up to nine active colleagues of the current workspace are all free, over one to seven local days (date defaults to today). Uses the same busy data as planner_get_availability, including imported external calendars, inside working hours day_start..day_end (default 09:00-18:00, caller's zone), weekends skipped unless include_weekends. buffer_minutes keeps a gap around busy time. Returns slots only, never anybody's event details; check external_included before promising a slot is truly free. Does not book.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "planner_suggest_slots"
  }
}

Input Schema

Name	Required	Description
`date`	No	Local YYYY-MM-DD; defaults to today.
`days`	No
`day_end`	No	HH:MM, default 18:00.
`user_ids`	No	Participants; the caller is always included.
`day_start`	No	HH:MM, default 09:00.
`buffer_minutes`	No
`duration_minutes`	No
`include_weekends`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real value beyond them: shared busy data with imported external calendars, working-hour clamping, weekend skipping, buffer behavior, and a privacy guarantee that only slots are returned. The one soft spot is referencing "external_included" without saying it comes from a prior availability call.

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?

Front-loaded with the core action and complete in a handful of clauses, with no filler. It is dense and slightly run-on (defaults and caveats interleaved), but every clause carries information an agent needs.

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?

No output schema exists, and the description compensates by saying exactly what comes back (slots only, no event details) and flagging the external_included caveat. Only minor gaps remain: what a returned slot looks like, ordering, and where external_included should be read from.

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?

With 50% schema coverage, the description does useful work: it supplies defaults (date=today, 09:00-18:00 in the caller's zone), the nine-colleague cap, the day range, and buffer semantics. It never mentions duration_minutes or the 15-480 bounds, leaving a meaningful parameter explained only by its bare schema type.

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?

States a specific verb+resource ("suggest the earliest meeting slots") plus the exact scope (caller plus up to nine active colleagues, one to seven local days). It also implicitly separates itself from booking ("Does not book") and from raw availability ("same busy data as planner_get_availability"), so an agent can pick it without opening another schema.

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 a clear when-to-use condition (everyone must be free) and a when-not signal ("Does not book"), with a caution to check external_included before promising a slot. It never routes to a sibling such as planner_free_slots for the single-user/other case, so the exclusion is incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OrgLines tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?