Skip to main content
Glama

Business details

get_business
Read-onlyIdempotent

One business in full: phone, address, website, opening hours and whether it's open now, holiday hours, emergency calls, services, towns it serves, state license numbers and expiry, and whether the owner has claimed the listing. Give either the id from search_businesses or a TownIndex page url.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe business id from search_businesses.
urlNoA TownIndex business page, e.g. https://townindex.org/asap-plumbing-and-heating-from-wolcott-ct/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by disclosing the returned data surface, including computed fields like "whether it's open now" and license expiry, though it says nothing about behavior on invalid id/url.

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

Conciseness4/5

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

Front-loaded with the purpose in the first clause, then the field inventory, then the input contract. The field list is long but every item is informative; no filler sentences.

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 field enumeration is essential and present, and the input contract is spelled out. The only gap is unstated failure behavior for a bad id or url, which is minor for a read-only lookup.

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% and both parameters are already documented, so the baseline is 3. The description still adds meaning by framing them as alternatives ("either the id ... or a ... url") and tying the id to the search_businesses output.

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?

"One business in full" states a specific resource and retrieval scope, immediately differentiated from the sibling list/search tool by the field enumeration. An agent can tell this is the single-record detail lookup without opening the schema.

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?

The closing sentence tells the agent exactly what inputs are acceptable (an id from search_businesses or a TownIndex page url), which implies the workflow search-then-fetch. There is no explicit statement of when not to use it or what happens with an unknown id, so it falls short of a 5.

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