LobbyStack

Get business profile

get_business

Read-onlyIdempotent

Returns the business name, time zone, default caller language, website, opening hours and booking_mode. Call this first: other tools return times in UTC, and booking_mode decides whether book_appointment and reschedule_appointment can work (they need instant).

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

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`id`	Yes	Stable identifier (UUID).
`name`	Yes
`hours`	Yes
`locale`	Yes	Default language for callers: en, fr, es, sr (Serbian, Latin script), de, pt (Brazilian Portuguese), it, nl, pl, tr, vi, tl (Tagalog), sv, ru or uk.
`timezone`	Yes	IANA time zone, for example America/Toronto.
`created_at`	Yes	ISO 8601 timestamp in UTC.
`updated_at`	Yes	ISO 8601 timestamp in UTC.
`website_url`	Yes
`booking_mode`	Yes	instant: appointments are booked directly. request: the receptionist takes a request and the team confirms it. off: no booking.
`business_type`	Yes	What kind of business it is. The dashboard uses service_company.
`onboarding_stage`	Yes	Where the business is in onboarding, for example website, phone_number or complete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so safety is covered. The description adds genuinely useful context beyond that: the UTC caveat on other tools and the fact that booking_mode determines whether two named sibling tools can function at all. It stops short of saying whether the profile can change mid-session or when it should be re-fetched, which keeps it from a 5.

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, no filler. The returned-field list comes first and the imperative 'Call this first' plus its justification follows, so the operational instruction is front-loaded where an agent will act on it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description needn't restate return structure; it focuses on the semantics an agent needs — the UTC baseline and the booking_mode gate. For a zero-parameter read with full annotation coverage, nothing required to call or use the result is missing.

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?

The tool takes no parameters, so the baseline is 4 and there is no schema semantics to add to. The description correctly spends no words on parameters and instead uses the space for return-value meaning.

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 ('Returns') and enumerates the concrete fields delivered (business name, time zone, default caller language, website, opening hours, booking_mode). This clearly separates it from the entity-specific siblings like get_appointment and get_contact, which return records rather than profile/config data.

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

Usage Guidelines5/5

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

Explicitly instructs 'Call this first' and gives the reason: other tools return times in UTC, so this call is needed to interpret them. It also states a downstream consequence — booking_mode must be 'instant' for book_appointment and reschedule_appointment to work — which tells the agent when this tool gates the use of alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LobbyStack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?