Skip to main content
Glama

Subscription Change Proration

bpj_subscription_proration
Read-onlyIdempotent

Prorate the unused old plan and remaining new plan over the actual days left in the billing cycle.

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": {
      "old": "<old>",
      "updated": "<updated>",
      "remaining": "<remaining>",
      "days": "<days>"
    },
    "name": "bpj_subscription_proration"
  }
}

Input Schema

NameRequiredDescriptionDefault
oldYes
daysYes
updatedYes
remainingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and determinism are covered. The description adds a real behavioral detail beyond them: the proration is based on 'actual days left in the billing cycle' rather than a standardized 30-day month, which affects the expected result. It stops short of disclosing the formula or the return shape.

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 front-loaded sentence with no filler or repetition. It is efficient, though the extreme brevity leaves no room for the clarifying detail the tool actually needs.

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-required-parameter numeric calculator with no output schema, the definition conveys the intent but not the contract: it never states what is returned (a single prorated amount, a delta, or two line items) or the currency/rounding assumptions. Adequate to recognize the tool, thin for invoking it confidently.

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 must carry the burden, and it only partially does. It conceptually maps to the parameters ('unused old plan' → old, 'remaining new plan' → updated, 'days left in the billing cycle' → days/remaining) but never explains units (currency vs. percent), whether charges are monthly, or how 'days' and 'remaining' interact in the formula.

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 uses a specific verb ('Prorate') on a specific resource ('unused old plan and remaining new plan') within a defined scope ('actual days left in the billing cycle'). An agent knows this is a mid-cycle subscription change proration calculation. It does not name or differentiate itself from any sibling calculator, which keeps it at 4 rather than 5.

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 guidance, no preconditions, and no mention of when-not-to-use this tool. Given dozens of other finance-related calculators among the siblings, an agent gets no help deciding whether proration is the right calculation versus adjacent tools like payback or schedule-impact variants.

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.