Skip to main content
Glama

VoiceAssistants

Get a business's facts

get_business
Read-onlyIdempotent

Get the facts on file for one business in the VoiceAssistants directory: what it is, where, phone, hours, and — for a premium listing — services with supplied prices, service area, credentials and live availability. Every fact comes from the business; source and last_verified say where and when. 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>"
    },
    "name": "get_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe business id from find_businesses, for example "seaside-plumbing-stuart-fl".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description earns credit for what it adds instead: that response richness is tier-dependent (services, prices, service area, credentials, availability appear only 'for a premium listing'), and that every fact carries provenance via `source` and `last_verified`. It never contradicts the read-only annotation but also doesn't cover failure behavior for an unknown id.

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 dense sentences: what is returned, where the data comes from and how it is verified, then the call/consumption instructions. Front-loaded with the resource and return payload; no filler or restated title.

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 carries the return-shape burden and does so by naming key fields (`source`, `last_verified`, `spoken`) and the premium/non-premium variance an agent must expect. Only gap is what happens on a missing or invalid id.

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?

The single `id` parameter has 100% schema description coverage that already states it comes from find_businesses with an example value. The description repeats 'Pass the `id` from find_businesses' without adding format, casing, or error semantics, so the schema does the substantive work.

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?

Specific verb plus resource ('Get the facts on file for one business in the VoiceAssistants directory') followed by an enumeration of the exact facts returned: identity, location, phone, hours, and premium-only services, prices, service area, credentials, availability. A single-business lookup is clearly distinguished from the sibling find_businesses, which is named.

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?

Explicitly routes the agent: 'Pass the `id` from find_businesses', making the search-then-fetch workflow unambiguous, and instructs 'Read `spoken` aloud', a concrete consumption rule. It does not state exclusions (e.g., use get_hours when only hours are needed), so it stops short of full alternative coverage.

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