Skip to main content
Glama

About the business

get_business
Read-onlyIdempotent

The business’s profile: what it sells, where it is, opening hours, how it sells (showroom, online store, bulk), whether it takes visits and has an online checkout, and its WhatsApp and chat links.

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

Input Schema

NameRequiredDescriptionDefault
businessYesThe business id from find_businesses, e.g. "carat-story".

Output Schema

NameRequiredDescriptionDefault
nameYes
hoursYes
phoneYes
sellsYes
websiteYes
chat_urlYes
locationYes
logo_urlYes
catalogueYes
descriptionYes
takes_visitsYes
whatsapp_urlYes
instagram_urlYes
google_maps_urlYes
online_checkoutYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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 the safety profile is fully covered by structured data. The description adds the substantive behavioral context that the response is a profile containing specific attribute categories, but says nothing about what happens for an unknown id, caching, or freshness of hours/links.

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?

One sentence, front-loaded with the resource ("The business's profile"), followed by a compact list of returned facets. It is dense but every clause names data the agent will actually receive, so there is little waste.

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 a full output schema and rich read-only annotations, the description only needs to convey scope, which it does by listing the profile facets. The main gap is the absence of any linkage to find_businesses or note on missing/unknown business ids, but for a single-parameter read tool this is close to complete.

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% and the single parameter is documented with a pattern, length bounds, and an example, so the schema carries full parameter meaning. The description adds no additional parameter semantics beyond what the schema already states.

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?

The description makes clear that this tool returns a business's profile, and it enumerates the specific facets returned (what it sells, location, hours, sales channels, visit policy, checkout, WhatsApp/chat links). The resource is unmistakable, though there is no explicit verb ("get"/"retrieve") and no differentiation from siblings such as get_product or find_businesses.

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

Usage Guidelines2/5

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

The description contains no when-to-use guidance, no prerequisites, and no alternatives. It never says this is the follow-up to find_businesses or contrasts itself with ask_business or search_products; the only routing hint ("business id from find_businesses") lives in the schema, not the description.

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