Skip to main content
Glama

Graduated Usage Bill

bpj_graduated_usage_bill
Read-onlyIdempotent

Calculate a two-tier graduated bill by pricing the first units at tier one and only the remainder at tier two.

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>",
      "threshold": "<threshold>",
      "tierOne": "<tierOne>",
      "tierTwo": "<tierTwo>"
    },
    "name": "bpj_graduated_usage_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierOneYes
tierTwoYes
thresholdYes
consumptionYes

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 establish that this is a read-only, idempotent, closed-world calculation. The description adds useful behavioral context by explaining that only units above the threshold are priced at tier two. It does not disclose rounding rules, currency assumptions, or what happens when consumption is below the threshold.

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?

The definition is a single efficient sentence with no wasted wording. The core tiering logic is front-loaded and immediately understandable.

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 pure-calculation tool, the description explains the core algorithm adequately. However, with no output schema and no parameter descriptions, it omits the return value shape, rounding behavior, and boundary handling, leaving meaningful gaps for an agent invoking the tool.

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. It conceptually explains how threshold, tier-one price, tier-two price, and consumption interact, but it never names the parameters, specifies units, or clarifies rounding or edge cases involving consumption below the threshold.

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 verb and resource: calculating a two-tier graduated bill. It also explains the tiering rule, making the computation distinguishable from a generic bill tool. It does not explicitly differentiate itself from close siblings such as bpj_metered_overage_bill or bpj_usage_commitment_true_up.

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 exclusions, and no mention of alternatives. An agent must infer that this tool applies to graduated two-tier pricing rather than metered overage or commitment true-up scenarios.

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.