Skip to main content
Glama

Minimum Commitment True-Up

bpj_usage_commitment_true_up
Read-onlyIdempotent

Compare metered charges with the contractual minimum and determine the shortfall charged at settlement.

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": {
      "spend": "<spend>",
      "minimum": "<minimum>"
    },
    "name": "bpj_usage_commitment_true_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
spendYes
minimumYes

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?

The annotations already declare this a safe, idempotent, closed-world read, so the description needn't restate safety. What it does add is that the tool performs a comparison against a contractual floor rather than returning a raw spend figure, but it never states the outcome when spend meets or exceeds the minimum (presumably zero shortfall) or whether any side effect occurs at settlement.

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 well-formed sentence with the comparison front-loaded and the output clause at the end; nothing is padded. It is dense enough that a slightly more structured phrasing (inputs, then result) would read faster, but there is no waste.

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 two-input read-only calculator with no output schema, the description covers the inputs and the concept but never describes the result shape (amount, zero, or negative) or edge behavior when spend exceeds the minimum. That missing return-value context is the main completeness gap for a tool with no output schema.

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 coverage is 0%, but the two parameters carry titles ('Usage charge', 'Minimum committed charge') and numeric bounds that make their roles largely self-evident. The description reinforces the relationship between them, yet adds no unit, currency, or period semantics beyond what the titles imply.

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 concrete verb pair (compare, determine) and a concrete resource (metered charges vs. contractual minimum) and states the business output, the shortfall charged at settlement. It does not distinguish itself from near-neighbors such as bpj_project_commitment_headroom, so an agent must reason about the boundary itself.

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?

The phrasing 'at settlement' hints at the billing context, but there is no explicit when-to-use statement, no precondition (e.g., only when spend is below minimum), and no named alternative for related headroom or graduated-billing questions.

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.