Skip to main content
Glama

Get business details

get_business
Read-onlyIdempotent

Get one business's public profile (city, address, hours, booking and cancellation policy, contact, FAQ) and its active services with prices, durations and weekly schedules. Use this after search_businesses, or when the user names a business, before checking open times. Read-only.

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": {
      "business_id": "<business_id>"
    },
    "name": "get_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYesbusiness_id from search_businesses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' in the description is mostly redundant. The real added value is disclosing the shape of the response payload (profile fields plus active services with prices and schedules), which no output schema provides. It omits failure behavior such as an unknown or stale business_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?

Two sentences, front-loaded with what is returned and then how it fits into a workflow. The parenthetical field list is dense but purposeful; nothing is filler. 'Read-only' is the only mildly redundant clause given the annotations.

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?

For a single-parameter lookup with no output schema, the description does the heavy lifting by enumerating returned fields and placing the call in a workflow. Safety and idempotency are covered by annotations. What remains unaddressed is error/not-found behavior and whether the response is paginated or truncated for businesses with many services.

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 the schema itself documents business_id as coming from search_businesses. The description reinforces this by saying to use the tool 'when the user names a business,' which implies a name-to-id resolution step through search_businesses before calling. Marginal but genuine added meaning over the schema.

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?

Names a specific verb and resource ('Get one business's public profile') and enumerates exactly what comes back: city, address, hours, policies, contact, FAQ, plus active services with prices, durations and weekly schedules. This clearly separates it from search_businesses, which only discovers businesses rather than returning a full profile.

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?

Gives concrete triggering conditions: 'after search_businesses, or when the user names a business, before checking open times.' That establishes both the discovery-to-detail workflow and the ordering relative to an availability lookup. It stops short of an explicit exclusion or naming get_availability as the alternative, so it is strong but not complete routing guidance.

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.