Skip to main content
Glama

find_meeting_time

Read-onlyIdempotent

Find ranked meeting time suggestions across structured locations, with an optional ISO or natural-language date resolved by the first location's timezone.

Instructions

Return ranked meeting suggestions from the production meeting search endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Paste shareText to the user. plannerUrl carries aiCities, up to three UTC aiSlots, legacy aiTime, and ref=mcp-bot. Do not invent wall-clock times. Route vague or mixed-intent raw prompts to answer_time_question.

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": "find_meeting_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date to anchor the meeting search. Prefer ISO YYYY-MM-DD, but simple human values such as "Thursday", "tomorrow", or "next Friday" are accepted.
locationsNo
_endUserIdNoOptional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID.
countryCodesNo
durationMinutesNoOptional meeting length. Only 30, 45, or 60 are written onto the planner link as aiDuration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.28.1
    • changedInput schema / properties / date / description
      Previous value: -"Optional ISO date to anchor the meeting search."New value: +"Optional date to anchor the meeting search. Prefer ISO YYYY-MM-DD, but simple human values such as \"Thursday\", \"tomorrow\", or \"next Friday\" are accepted."
    • addedInput schema / properties / durationMinutes
      Added value: +{
      +  "description": "Optional meeting length. Only 30, 45, or 60 are written onto the planner link as aiDuration.",
      +  "type": "integer"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "locations"
      -]
  2. First observedv3.27.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description goes further by disclosing that the server resolves relative dates against the first location timezone and that the response contains shareText and a plannerUrl carrying aiCities, aiSlots, aiTime and ref=mcp-bot. That is real output-shape information the agent would otherwise lack, since no output schema exists.

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 purpose, then guidance, then output/behavioral detail, with no filler sentences. Some phrasing is jargon-heavy ('plannerUrl carries aiCities, up to three UTC aiSlots, legacy aiTime') and would be opaque without prior knowledge of the product, which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly compensates by naming the key return fields and the instruction to paste shareText. Combined with the date-resolution behavior and the routing rule, an agent has enough to call this correctly and present results.

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 60%, so some burden falls on the description, and it does add meaning: human date values are resolved relative to the first location's timezone, and durationMinutes is only written onto the planner link as aiDuration. It leaves countryCodes and _endUserId entirely to the schema, which is acceptable since the schema documents them, but the description is not fully compensatory.

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 and resource: 'Return ranked meeting suggestions from the production meeting search endpoint', and scopes it to structured locations plus an optional date. An agent can distinguish it from answer_time_question and the other time siblings 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 Guidelines5/5

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

Gives an explicit positive condition ('Use when you have structured locations and, optionally, a date') and an explicit alternative with its selection rule ('Route vague or mixed-intent raw prompts to answer_time_question'). It also adds a guardrail directive ('Do not invent wall-clock times').

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