Skip to main content
Glama

book_call

Book a free 15-minute phone call at an open slot from list_call_slots. Status is confirmed only when the calendar accepts it.

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": {
      "business": "<business>",
      "contact_name": "<contact_name>",
      "email": "<email>",
      "phone": "<phone>",
      "start": "<start>"
    },
    "name": "book_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesWhere the report or calendar invite goes
notesNoAnything we should know
phoneYesNumber we call at the booked time
startYesSlot start, ISO 8601, exactly as listed
websiteNoBusiness website, if any
businessYesBusiness name
agent_nameNoWhich agent you are (e.g. product and version)
contact_nameYesThe person the booking is for (your human)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry behavior, and it does disclose an important trait: success is conditional, with status confirmed only if the calendar accepts the slot. It does not say what happens when the slot is rejected, whether retries or duplicate bookings are handled, or what permission/auth is required, leaving meaningful gaps for a mutation tool.

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?

Two compact sentences with the core action and the source of the slot front-loaded, and the conditional-confirmation caveat following. Little waste, though the second sentence is terse enough that it could have carried slightly more behavioral detail at the same length.

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 five-required-parameter write operation with no annotations and no output schema, the definition covers the action, the prerequisite data source, and the confirmation condition. What is left out is failure handling and what the confirmed booking returns, which matters but is a modest gap given the schema already documents inputs thoroughly.

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 every one of the eight parameters is already documented with guidance (e.g. start must be ISO 8601 'exactly as listed'). The description reinforces the slot-origin constraint but adds no format or validation detail beyond the schema, which is the expected baseline.

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 (book a free 15-minute phone call), plus the constraint that it must be at an open slot coming from list_call_slots. Duration, cost, and channel are all specified, so an agent knows exactly what operation this performs 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 Guidelines4/5

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

The clause "at an open slot from list_call_slots" implicitly tells the agent to fetch slots first, which is real usage context rather than none. It stops short of explicit exclusions or naming when a different booking path (e.g. other booking siblings) would be preferred, so it is clear context but not full when/when-not guidance.

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