Skip to main content
Glama

Subscription Migration Payback

bpj_subscription_migration_payback
Read-onlyIdempotent

Estimate simple payback from immediate monthly savings, one-time migration cost and temporary parallel running costs.

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": {
      "service": "<service>",
      "saving": "<saving>",
      "overlap": "<overlap>",
      "overlapMonths": "<overlapMonths>"
    },
    "name": "bpj_subscription_migration_payback"
  }
}

Input Schema

NameRequiredDescriptionDefault
savingYes
overlapYes
serviceYes
overlapMonthsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description is not burdened with safety disclosure. It adds that the result is a 'simple payback' built from immediate savings, one-time cost, and temporary parallel-running cost, but leaves the actual formula (how the overlap rate times months is combined) and the output shape undefined.

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?

A single front-loaded sentence with no filler; every clause introduces a distinct input or the output concept. Nothing could be removed without losing meaning.

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 four-parameter calculator with no output schema and no parameter-level documentation, the definition covers the inputs conceptually but omits the payback formula, the role of the overlap months, and any note on currency/units of the returned value. Adequate to identify the tool, thin on how to interpret its result.

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?

Schema description coverage is 0%, so the description carries real weight and does map its three cost concepts onto the four parameters: monthly savings, one-time migration cost, and parallel running cost/months. However, it never clarifies that the oddly named 'service' parameter is the one-time migration cost, nor whether 'overlap' is a monthly rate multiplied by 'overlapMonths'.

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 names a specific verb and resource — 'Estimate simple payback' for a subscription migration — and lists the three cost components it consumes, so the agent knows exactly what calculation is performed. It does not explicitly differentiate itself from siblings, but its scope is unambiguous.

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 when-to-use, when-not-to-use, or alternative guidance; the agent must infer that this is the payback calculator to call when comparing migration savings against costs. No prerequisites, assumptions, or boundary conditions are stated.

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.