Skip to main content
Glama

VoiceAssistants

Ask a business to call back

request_callback

Ask one business in the VoiceAssistants directory to call the person back. This sends the person's name and phone number to that business. BEFORE calling this tool, say the business's name and the phone number back to the person and get a clear yes; then set consent to true. Only some businesses take callback requests — if this one does not, the result says so and gives its phone number instead. Read spoken aloud.

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": {
      "id": "<id>",
      "name": "<name>",
      "phone": "<phone>",
      "consent": "<consent>"
    },
    "name": "request_callback"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe business id from find_businesses.
nameYesThe person's name, as they want the business to address them.
noteNoOptional: what the call is about, in a sentence.
phoneYesThe phone number the business should call, with area code.
consentYesMust be true: the person has just confirmed, in this conversation, that they want this business to contact them at this number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent but non-destructive action, and the description adds the meaningful extra facts: it transmits the person's name and phone number to a third party, requires verbal consent, and returns a `spoken` string meant to be read aloud. It does not cover failure modes beyond the unsupported-callback case (e.g. bad id, incomplete phone), which keeps it at solid-but-not-complete.

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-loads the action, then the data disclosure, then the consent gate, then the fallback, then the output instruction. Five short sentences, each adding distinct operational value with no 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?

With no output schema, the description steps in to describe the fallback shape (result says the business does not accept requests and gives its phone number) and the `spoken` output, which is the right compensation. Minor gap: the success-case result shape beyond `spoken` is not characterized.

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 the schema already documents every field, including the consent semantics verbatim, so the description adds little beyond restating the consent gate. Baseline 3 applies since the schema carries the parameter burden.

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 with scope ('Ask one business in the VoiceAssistants directory to call the person back'), which cleanly separates it from siblings like request_quote and answer_question that also target a single business.

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 pre-call procedure (say the business name and phone number back, get a clear yes, then set consent=true) plus the branching case where the business does not accept callbacks and the result returns a phone number instead. Nothing about when to use it is left to inference.

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