Skip to main content
Glama

Coline

Find time

find_time
Read-onlyIdempotent

Suggests open times on the person's calendar for something of a given length, within their working hours, over the next two weeks at most.

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>",
      "durationMinutes": "<durationMinutes>"
    },
    "name": "find_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueDateNoPrefer times before this.
maxSlotsNo
priorityNo
rangeEndNoDefault five working days after the start; at most 14 days.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
rangeStartNoDefault now.
durationMinutesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that — results are confined to working hours and capped at a two-week horizon — but says nothing about whose availability is searched, whether only the caller's own calendar is used, or how many candidates come back.

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 sentence, front-loaded with the verb and resource, with the three constraints packed as modifiers. No filler, though the stacked qualifying clauses make the sentence slightly dense and the phrase "the person's" costs clarity.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. For a 7-parameter read tool the description covers purpose and the key bounding constraints adequately; the remaining gap is the undocumented maxSlots and priority parameters and the missing tie to sibling tools.

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 coverage is 57%, so the schema documents workspace, dueDate, rangeStart and rangeEnd but leaves maxSlots, priority and durationMinutes undescribed there. The description supplements durationMinutes ("something of a given length") and echoes the 14-day ceiling that rangeEnd already states, but adds no meaning for maxSlots or priority, so it only partially compensates for the coverage gap.

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 and resource ("suggests open times on the person's calendar") plus the qualifying constraints (given length, working hours, two-week horizon). An agent can distinguish it from a discovery tool like find_people, but it never distinguishes it from the obvious alternatives in the sibling list (check_availability, propose_new_time), and "the person's" leaves ambiguous whose calendar is being read.

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 only implied: the two-week cap and working-hours scope suggest this is a pre-proposal slot search rather than a booking action, but the description never states when to use this versus check_availability or propose_new_time, nor any prerequisite (e.g. that a workspace and a duration are required).

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