Skip to main content
Glama

Coline

Pick a time for a booking request

accept_booking_request
Destructive

Books one of the times someone offered through a scheduling link, and tells them.

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>",
      "linkId": "<linkId>",
      "requestId": "<requestId>",
      "openingId": "<openingId>"
    },
    "name": "accept_booking_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkIdYesScheduling link id from list_scheduling_links.
openingIdYesThe offered time to book.
requestIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is structured rather than textual. The description does add one piece of context beyond that: 'and tells them', which discloses a notification side effect to the requester. It never explains what makes the call destructive, whether other openings are invalidated, or whether the booking can be undone, so it is helpful but far from complete.

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?

A single sentence that front-loads the action and wastes no words. It is efficient, though the brevity edges toward under-specification for a destructive mutation rather than pure conciseness.

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

Completeness3/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. However, this is a non-idempotent destructive write with four required parameters, and the description says nothing about consequences, required permissions, or failure modes. For a mutation of this weight, the definition is thinner than it should be.

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 75%, with linkId, openingId, and workspace already documented inline; requestId has no schema description. The description adds no parameter-level meaning at all, only the notion of 'the offered time' matching openingId. With coverage this high, a baseline 3 is appropriate, though requestId remains undocumented in both places.

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 gives a specific verb and resource: it books one of the times offered through a scheduling link. An agent can tell this is the confirm-a-time action rather than the propose-new-time or find-time action. It stops short of explicitly naming a sibling, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description states the situation (someone offered times via a scheduling link) but never says when to choose this over the closely named sibling answer_proposed_time, nor when not to use it. There are no prerequisites or exclusions, so the agent has to infer the routing decision.

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