Skip to main content
Glama

estimate_ai_roi

Read-onlyIdempotent

Use when building an internal AI business case, portfolio tracker or ROI dashboard. Returns cash flow, NPV, payback and sensitivity cases with recovered capacity separated from realised cash savings.

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": {
      "useCase": "<useCase>",
      "users": "<users>",
      "minutesPerTask": "<minutesPerTask>",
      "tasksPerUserPerMonth": "<tasksPerUserPerMonth>",
      "savings": "<savings>",
      "hourlyCost": "<hourlyCost>",
      "buildCost": "<buildCost>",
      "monthlyRunCost": "<monthlyRunCost>",
      "adoptionMonths": "<adoptionMonths>",
      "horizonMonths": "<horizonMonths>",
      "annualDiscountRate": "<annualDiscountRate>",
      "cashRealisation": "<cashRealisation>",
      "currency": "<currency>"
    },
    "name": "estimate_ai_roi"
  }
}

Input Schema

NameRequiredDescriptionDefault
usersYes
savingsYes
useCaseYes
currencyYes
buildCostYes
hourlyCostYes
horizonMonthsYes
adoptionMonthsYes
minutesPerTaskYes
monthlyRunCostYes
cashRealisationYes
annualDiscountRateYes
tasksPerUserPerMonthYes

Output Schema

NameRequiredDescriptionDefault
resultYes
generatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured context that recovered capacity is reported separately from realised cash savings, and that sensitivity cases are produced. It says nothing about the calculation model, validation rules (e.g., low ≤ base ≤ high, discount rate as a fraction up to 10), or failure modes for 13 required inputs.

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?

Two sentences, no filler, and the return-value content is front-loaded. The opening leads with usage context rather than the core purpose, so the first sentence is slightly less useful than the second for identification, but nothing is wasted.

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

Completeness2/5

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

High complexity: 13 required parameters, a nested object, an output schema (so return values need no explanation), and rich annotations. Given 0% schema description coverage, the description should explain at least the ambiguous financial inputs and unit conventions (percent vs fraction, currency code format). It supplies almost none of that, leaving the agent to guess at a dozen required fields.

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% across 13 required parameters, including a nested savings object with low/base/high and a cashRealisation fraction, so the description carries the full burden of explaining them. Instead it explains none of them beyond a loose hint that cash realisation affects separation of capacity versus cash. An agent cannot tell from this text what cashRealisation or annualDiscountRate mean or how the three savings levels interact.

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 enumerates concrete outputs (cash flow, NPV, payback, sensitivity cases) which pins down what the tool produces, and the 'recovered capacity separated from realised cash savings' clause adds a distinguishing nuance. It never states the verb directly ('estimates AI ROI') and does not name or rule out any sibling such as estimate_ai_project_cost, so differentiation is only partial.

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?

'Use when building an internal AI business case, portfolio tracker or ROI dashboard' gives clear situational triggers for invocation. There are no explicit exclusions or named alternatives (e.g., when to prefer estimate_ai_project_cost for a pure cost estimate), so the agent must infer the boundary itself.

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.