Skip to main content
Glama

Subscription Add-On Adoption Forecast

bpj_addon_adoption_forecast
Read-onlyIdempotent

Apply expected add-on adoption to active accounts and calculate incremental monthly and annual run-rate revenue.

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": {
      "active": "<active>",
      "uptake": "<uptake>",
      "upgradePrice": "<upgradePrice>"
    },
    "name": "bpj_addon_adoption_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeYes
uptakeYes
upgradePriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the result includes both monthly and annual run-rate revenue, which is useful, but it omits currency/units, rounding, and the exact calculation assumptions.

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?

A single well-formed sentence with no filler, and the core action is front-loaded. It is efficient, though its brevity contributes to missing semantic detail elsewhere.

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 simple three-parameter calculation with annotations covering safety and no output schema, the definition is minimally adequate. However, a calculation tool should ideally state the formula and unit conventions so an agent can trust the result without inference.

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 must carry parameter meaning. It references active accounts and adoption, but does not explain the price parameter, the percent scale for uptake, or that all three inputs are required and combined multiplicatively.

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 action: applying an adoption rate to active accounts and computing incremental monthly and annual run-rate revenue. This is clearly more than a restatement of the name, though it does not explicitly differentiate itself from sibling forecasting tools such as subscription migration payback or proration.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any stated preconditions or exclusions. The forecasting context is implied by the purpose, but an agent receives no routing 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.