Skip to main content
Glama

Growth Business Finance

Book a call with Growth Business Finance

book_call
Idempotent

Use this only when the user has chosen one of the slots from get_available_slots and asked to book it. It books a 30 minute Google Meet call with the broker at Growth Business Finance and sends a calendar invite to the email address given in the enquiry. Before calling: confirm the chosen date and time with the user and get their explicit go-ahead. If the slot has just been taken it returns fresh slots and books nothing. One call can be booked per enquiry; repeating the call does not create a second booking.

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": {
      "booking_token": "<booking_token>",
      "slot_id": "<slot_id>"
    },
    "name": "book_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
slot_idYesThe slot_id of the slot the user chose, from get_available_slots.
booking_tokenYesThe booking_token returned by submit_enquiry. Never ask the user for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=true and openWorld=true, yet the description still adds substantial new behavior: an invite is sent to the enquiry email, a taken slot returns fresh slots and books nothing, and one booking per enquiry is enforced. The only redundancy is the idempotency sentence, which largely restates idempotentHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the strict use condition, then side effects, then the pre-call checklist, then edge-case behavior. No filler sentences; each one carries a distinct operational fact.

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 still tells the agent what happens on the success path (Meet call + calendar invite) and on the failure path (fresh slots returned, nothing booked). Combined with annotations and full schema coverage, an agent has everything needed 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 coverage is 100% and both slot_id and booking_token are fully documented in the input schema, including the instruction never to ask the user for the token. The description adds only a mild clarification that the invite email comes from the enquiry rather than a parameter, so baseline 3 applies.

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 (books a 30 minute Google Meet call with the broker at Growth Business Finance) plus the trigger condition. It is clearly distinguishable from get_available_slots (which only lists) and submit_enquiry (which supplies the token).

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 gating rule ('Use this only when the user has chosen one of the slots from get_available_slots and asked to book it') and names the alternative path implicitly via get_available_slots. It also specifies a mandatory pre-call sequence: confirm date/time and obtain explicit go-ahead.

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