Skip to main content
Glama

VoiceAssistants

Answer a question about a business

answer_question
Read-onlyIdempotent

Answer a specific question about one business in the VoiceAssistants directory — for example "do they take emergency calls?", "are they licensed?", "do they serve Palm City?", "how much is a drain cleaning?" — from the answers on file for it. Answers are the business's own, or restate a fact it supplied; nothing is guessed. If the answer is not on file, answered is false and spoken says so and gives the phone number. Pass the id from find_businesses. 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>",
      "question": "<question>"
    },
    "name": "answer_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe business id from find_businesses.
questionYesThe question, in the person's own words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses provenance ("Answers are the business's own, or restate a fact it supplied; nothing is guessed") and the missing-data behavior (`answered` is false and `spoken` supplies the phone number). It even surfaces output field names despite there being no output schema, which is genuinely useful for an agent that must speak the result.

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 core purpose, then examples, then provenance and fallback, then the invocation instructions. Each sentence adds a distinct piece of information, and the four short examples clarify scope without padding.

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 two-parameter read tool with no output schema, the description covers everything an agent needs: scope, id source, provenance guarantee, failure mode with its return fields, and the requirement to read `spoken` aloud.

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 both parameters are already documented. The description reinforces the `id` source and notes the question should be "in the person's own words," but adds little syntax or format detail beyond the schema; baseline 3 applies.

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?

Uses a specific verb and resource ("Answer a specific question about one business") and grounds it in the VoiceAssistants directory, with four concrete example questions that make the intended granularity unmistakable. It does not explicitly contrast itself with get_business or get_hours, so it falls short of full sibling differentiation.

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?

"Pass the `id` from find_businesses" and "Read `spoken` aloud" give clear invocation and downstream-use guidance, and the not-on-file branch tells the agent what to expect. There is no explicit when-not or alternative routing (e.g., use get_hours for structured hours lookups), so selection guidance is clear but not complete.

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