Skip to main content
Glama

VoiceAssistants

Send a quote request to a business

request_quote

Send one business in the VoiceAssistants directory a request for a price quote: what the job is, when the person would like it done, and how to reach them. This sends the person's name, phone number and the job details to that business. BEFORE calling this tool, read the business's name, the job and the phone number back to the person and get a clear yes; then set consent to true. Only some businesses take quote 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>",
      "service": "<service>",
      "details": "<details>",
      "consent": "<consent>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe business id from find_businesses.
nameYesThe person's name, as they want the business to address them.
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.
detailsYesThe job in the person's own words: what is wrong or what they want done.
serviceYesThe service wanted, for example "water heater replacement".
preferred_timeNoOptional: when they would like the work done, for example "this week" or "Saturday morning".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses that personal data (name, phone number, job details) leaves the system to a third party, imposes a consent gate tied to an in-conversation confirmation, and describes the failure-mode result including the returned phone number. It also instructs the agent to read the `spoken` field aloud, revealing an output field that has no output schema to document it.

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?

Three sentences, front-loaded with the action and payload, then the mandatory consent procedure, then the edge case and output-handling instruction. Every clause carries information an agent needs before calling.

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?

For a write operation with six required parameters and no output schema, the description covers the payload, the consent prerequisite, the not-supported fallback, and how to handle the spoken result. Nothing essential to calling it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines all seven parameters; the description still adds procedural meaning by tying `consent` to a specific read-back-and-confirm step and clarifying that `details` should be in the person's own words. It does not add anything further for `id`, `phone`, or `preferred_time`.

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 names a specific verb and resource ('Send one business ... a request for a price quote') and scopes it to exactly one business in the VoiceAssistants directory. It does not explicitly say how this differs from the sibling request_callback, so the agent must infer the distinction from the payload described.

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 an explicit precondition sequence (read the business name, job and phone number back, get a clear yes, then set consent to true) and a documented fallback for businesses that do not accept quote requests. What is missing is any statement of when to choose this versus request_callback.

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