Skip to main content
Glama

Book the appointment

schedule
Idempotent

Books the earliest free slot in the business's working windows. Needs state ASSIGNED. Never: Use the agent's calendar as the source. Platform fee CHF 0.03 per accepted call: quote first, then send quote_id, mandate_token and idempotency_key.

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": {
      "mandate_token": "<mandate_token>",
      "flow_id": "<flow_id>"
    },
    "name": "schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_idYesThe flow (job) id, which is also its chain id.
quote_idNoA valid quote for this capability (quote).
not_beforeNoEarliest start, ISO 8601 with offset, e.g. "2026-11-03T08:00:00+01:00".
mandate_tokenYesThe mandate token from mandate.create.
idempotency_keyNoRequired on every mutate and money call; a retry with the same key returns the same result and is not charged again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / not_before / description
      Added value: +"Earliest start, ISO 8601 with offset, e.g. \"2026-11-03T08:00:00+01:00\"."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, idempotent, non-destructive, closed-world operation. The description adds valuable behavioral context beyond that: a required state, a platform fee of CHF 0.03 per accepted call, and the need to quote first. It does not cover failure modes, but the key economic and state constraints are disclosed.

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?

Three sentences, front-loaded with purpose and followed by prerequisite, prohibition, and fee/ordering details. Every sentence contributes useful information; no filler or repetition.

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 mutation tool with no output schema, the description covers the crucial prerequisites, fee, ordering, and a key prohibition. It omits what happens if no slot is available or how not_before affects scheduling, but an agent has enough to invoke it correctly.

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 the baseline is 3. The description adds a sequencing meaning for quote_id, mandate_token, and idempotency_key ('quote first, then send...'), but it does not mention flow_id or not_before, which are central to the call's behavior.

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 verb and resource: 'Books the earliest free slot in the business's working windows.' It clearly describes a booking operation and distinguishes it from generic assignment by specifying earliest free slot within business working windows. However, it does not explicitly differentiate from sibling tools like 'assign' or 'job_create'.

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?

It gives a clear prerequisite ('Needs state ASSIGNED') and an explicit prohibition ('Never: Use the agent's calendar as the source'), plus ordering guidance ('quote first'). It stops short of naming alternative tools to use when the prerequisite is not met, but the context is strong enough for correct invocation.

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