Skip to main content
Glama

Business review

business_review
Read-onlyIdempotent

Explains or calculates unit economics, revenue reconciliation or budget pacing from explicit inputs. Missing inputs are optional and stay missing: no example, cost, target or date is added. Every supplied number carries a verbatim quote from a user message or a source tool result; assistant examples and Knowledge instructions are not accepted as sources, and the tool checks the quotes, not their business meaning. A generic AOV is not treated as verified net first-order revenue. Pacing counts complete elapsed days only. Figures are combined only when their currency, definition and window match. responseMode=answer returns a report; evidence returns the underlying data. No writes or forecasts.

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": {
      "input": "<input>"
    },
    "name": "business_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent, non-destructive), it discloses that every number needs a verbatim quote that is machine-checked not semantically checked, that assistant examples and Knowledge instructions are rejected as sources, and that no writes or forecasts occur. This is substantive behavior a caller could not infer from the readOnly hint alone.

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?

The opening sentence front-loads what the tool does and the rest are short, dense rule statements. A few clauses (e.g. the AOV caveat) restate schema descriptions, but nothing is filler and the ordering follows what a caller needs first.

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?

For a nested, three-variant schema with no output schema, the description covers input philosophy, evidence validation, pacing semantics, and both response modes. Remaining gaps are minor, such as what fields the 'answer' report or 'evidence' payload actually contain.

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?

With 75% schema coverage the baseline is high, but the description still adds meaning: responseMode 'answer returns a report; evidence returns the underlying data', and the note that a generic AOV is not treated as verified net first-order revenue clarifies the netRevenuePerOrder parameter's intent. Optional/omitted input behavior is also spelled out.

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 specific verbs and three distinct resources ('unit economics, revenue reconciliation or budget pacing') and adds the 'from explicit inputs' scope, so an agent can tell what the tool does. It does not name or differentiate itself from plausible siblings such as planning_calculate or metric_compare, leaving that distinction to the schema.

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

Usage Guidelines4/5

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

It gives clear operating conditions: missing inputs stay missing, only complete elapsed days count for pacing, and figures are combined only when currency/definition/window match. These tell the agent when the tool applies and what it will refuse to do, but there is no explicit routing against alternatives like planning_calculate.

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.