Skip to main content
Glama

Metered Overage Bill

bpj_metered_overage_bill
Read-onlyIdempotent

Add a fixed plan fee and charge the overage rate only on consumption above the included allowance.

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": {
      "consumption": "<consumption>",
      "included": "<included>",
      "extra": "<extra>",
      "base": "<base>"
    },
    "name": "bpj_metered_overage_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
extraYes
includedYes
consumptionYes

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral content beyond that by specifying that overage is charged only on the excess above the allowance, which defines the edge case when consumption is at or below the allowance. It says nothing about edge behavior for negative results, rounding, or units, and no output schema exists to cover the return value.

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?

One sentence, front-loaded with the fee-then-overage structure, with no filler or repetition of the title. It is efficient, though the brevity is partly the source of the gaps in usage guidance and return-value description.

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

Completeness4/5

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

For a pure four-number arithmetic tool with annotations covering safety, the description conveys the formula's shape accurately: fee plus rate times excess. The main omissions are the returned value (evidently a single bill amount, unstated) and rounding or currency conventions, which are minor for a calculation of this simplicity.

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 parameter meaning, and it partially does: 'fixed plan fee' maps to base, 'overage rate' to extra, and 'included allowance' to included, with the relationship between extra and included spelled out. However, 'consumption' ('Usage this period') is never referenced in the description, and no units or magnitude expectations are given for any of the four required numbers.

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 concrete computation: a fixed fee plus an overage rate applied only to consumption above an included allowance, which maps cleanly onto the tool's name and title. An agent can tell this is a billing formula rather than a parser or formatter. It does not explicitly distinguish itself from the close sibling bpj_graduated_usage_bill (tiered pricing), leaving that differentiation to inference from the names.

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 or when-not guidance, no mention of prerequisites, and no pointer to the graduated/tiered alternative that would be the natural competing choice. The only implicit context is that this models flat-fee-plus-single-overage-rate pricing, which the agent must derive from the formula 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.