Skip to main content
Glama

Get business overview

get_business_overview
Read-only

Get a summary of the guide's business: profile, team guides (id, name, role, and active flag), services, client and activity counts, booking status counts, upcoming bookings, and finance totals.

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_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, non-destructive, closed-world operation, so the description does not need to restate that. It adds useful behavioral detail by disclosing the composition of the returned summary, including team guides, service data, counts, bookings, and finance totals, though it does not discuss freshness, limits, or permissions.

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?

The description is a single front-loaded sentence that states the action and then lists the content categories with no filler. Despite the long enumeration, every listed item contributes to understanding the tool's return scope.

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?

Because there is no output schema, the description appropriately compensates by enumerating the summary contents. It is complete enough to invoke correctly, though it omits freshness, pagination, and explicit routing versus narrower sibling tools.

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?

There is only one optional parameter, business_id, and schema description coverage is 100%, so the schema already explains its meaning and the single-business default. The description does not add any further parameter guidance beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource, "Get a summary of the guide's business," and enumerates the included data categories so the agent knows this is an aggregate overview tool. It is clear, but it does not explicitly differentiate itself from narrower sibling tools such as get_finance_summary or get_activity.

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 by the phrase "summary" and the broad content list, which suggests this tool is for a full business snapshot rather than a single-entity lookup. However, it gives no explicit when-to-use, when-not-to-use, or sibling alternative 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.

Resources