Skip to main content
Glama

Revenue scenario model

privi_pro_revenue_forecast
Read-only

Estimate gross monthly revenue from prospective customers and conversion. PAID ONLY: 5 prepaid credits; production billing required.

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": {
      "leads": "<leads>",
      "conversion_pct": "<conversion_pct>",
      "average_order_usd": "<average_order_usd>"
    },
    "name": "privi_pro_revenue_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadsYes
conversion_pctYes
average_order_usdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare a pure read with openWorldHint=false, so the safety profile is covered. The description adds a real behavioral fact the annotations do not: the call is metered at 5 prepaid credits and requires production billing, which affects whether an agent should invoke it. It says nothing about the assumptions of the projection or the shape of the result.

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 short sentences, front-loaded with what is computed and followed immediately by the cost gate. No filler and nothing buried.

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

Completeness3/5

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

For a three-parameter calculator with no output schema the description is serviceable, naming the metric produced and the billing cost. It stops short of stating units, valid ranges, or whether the estimate is a single monthly figure, which an agent needs to construct valid inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it only loosely maps prose ("prospective customers," "conversion") onto the three fields. Critically, it never states whether conversion_pct is a fraction or a percentage, nor the currency basis for average_order_usd, which are the two most likely sources of a wrong call.

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?

A concrete verb-plus-resource: "Estimate gross monthly revenue from prospective customers and conversion." An agent can tell this is a revenue projection from leads and conversion rate, but nothing here distinguishes it from sibling estimators like privi_pro_model_cost_estimate or privi_pro_stripe_fee_scenario.

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?

No statement of when to prefer this forecast over other scenario tools, nor any prerequisites beyond the billing note. The agent must infer from the name alone that this is the revenue-side counterpart to the cost and fee estimators.

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.