Skip to main content
Glama

Belline Connect

Get a business's profile

get_business_profile
Read-onlyIdempotent

One business: what it does, hours, languages, whether it books a real diary or confirms every request itself, how long it has to answer, and its services with price ranges, callout fee and emergency surcharge where the owner set them. Prices are the owner's own figures; a range means the owner confirms the exact price once the job is seen.

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": {
      "slug": "<slug>"
    },
    "name": "get_business_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe business slug from search_businesses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuine domain context beyond that: it discloses the booking-mode field, the owner response window, and crucially that prices are the owner's own figures with ranges meaning the exact price is confirmed after the job is seen.

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?

Two sentences, front-loaded with the record scope and then the returned fields; the pricing caveat is placed last where it belongs. The long comma-separated field list is dense but each item carries meaning, so nothing is padding.

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?

There is no output schema, so the description must characterize the return value, and it does so field by field, including the semantics of price ranges. For a one-parameter read tool this is close to complete; only error/not-found behavior is unaddressed.

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 there is a single required slug parameter already documented as coming from search_businesses. The description adds nothing about the slug itself, so this sits at the baseline for fully covered schemas.

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 names a specific resource (one business profile) and enumerates the payload an agent will get back: hours, languages, booking mode, response window, services with price ranges, callout fee and emergency surcharge. It implicitly contrasts with a multi-result search by saying 'One business', though it never states the retrieval verb outright or names search_businesses as its counterpart.

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 only implied: the singular framing signals a single-record lookup on a known business, versus the listing siblings. There is no explicit when-to-use / when-not-to-use guidance and no mention of how this differs from ask_business, get_availability or get_inquiry_status when an agent already has a slug.

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