Skip to main content
Glama

Get business

get_business
Read-onlyIdempotent

The full record of one business (code) or up to 10 (codes): location, description, opening hours (OpenStreetMap format), its website in detail (what it is built with, last update, https, mobile version, online store, booking system, travel sites, delivery apps, payments, chat, analytics and ad pixels), social profiles, attributes with their source (services, prices, how it takes bookings) and its contacts. No credits, up to 300 a day (20 until the account buys credits); revealed ones don't count. Contacts stay masked and social profiles hidden (value null, hidden true) until revealed.

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
codeNoBusiness code, from search_businesses
codesNoSeveral codes at once (max 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses credit economics ('No credits... revealed ones don't count'), a rate limit (300/day, 20 until credits are purchased), and the masking contract (contacts/socials return value null and hidden true until revealed). These are exactly the operational facts an agent cannot get from structured fields.

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?

Purpose is front-loaded in the first clause and the caveats (credits, limits, masking) come last, which is the right ordering. The long parenthetical inventory of website sub-features (analytics, ad pixels, chat, travel sites) is dense and borders on padding, but it does convey the record's breadth.

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 usefully enumerates the returned record's shape and the masking behavior, and it covers cost and rate limits. The remaining gap is edge behavior: what happens with an unknown or expired code, or with both parameters at once.

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 coverage is 100% and both parameters are already documented, including the max-10 bound. The description only restates the one-code vs many-codes distinction and never clarifies whether 'code' and 'codes' can be supplied together, so it adds little beyond the schema baseline.

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?

The description opens with a specific resource and verb: 'The full record of one business (code) or up to 10 (codes)'. It then enumerates what that record contains (location, hours, website stack, socials, attributes, contacts), which clearly separates it from the sibling search_businesses that produces the codes in the first place.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: you supply known codes, and the schema notes the codes come 'from search_businesses'. There is no explicit 'call this after search_businesses, not instead of it' routing, and the alternative reveal_contacts is never named even though the masking rule points straight at it.

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