Skip to main content
Glama

Progress Billing and Retainage

bpj_milestone_billing_retainage
Read-onlyIdempotent

Bill only the newly certified share of contract value and deduct the specified retention from the current certificate.

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": {
      "contract": "<contract>",
      "completed": "<completed>",
      "before": "<before>",
      "retention": "<retention>"
    },
    "name": "bpj_milestone_billing_retainage"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeYes
contractYes
completedYes
retentionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare this as a side-effect-free, idempotent, closed-world read, and the description is consistent with that: this is a calculation, not a write. It adds the incremental-certification logic (bill the delta, deduct retention from the current certificate), but says nothing about the return value's form, currency units, rounding, or how negative deltas are handled.

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?

This is a single front-loaded sentence that states the computation and the deduction without any filler. Every clause carries meaning.

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 four-parameter calculation tool with no output schema, the definition covers what the tool computes and how the inputs relate. It is somewhat incomplete because it neither describes the returned figure nor states the input units and edge cases. Still, an agent could call it plausibly without further information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, with only titles on the four parameters, so the description must carry the semantics, and it largely does. It explains that the billed amount is the newly certified share (implicitly completed minus before) and that retention is deducted from the current certificate. However, it never explicitly clarifies the completed-versus-before distinction or the units and precision of the inputs.

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 specific verbs and resources: bill the newly certified share of contract value and deduct retention from the current certificate. This makes the incremental progress-billing/retainage calculation clear. It doesn't need to distinguish itself from siblings, since the sibling names are unrelated utilities, so a 4 rather than a 5 is appropriate.

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 description implies the scenario (progress billing against a certificate) but gives no explicit when-to-use, when-not-to-use, or prerequisite guidance. For example, it doesn't say whether it handles a first certificate, in which 'before' is 0, or how it relates to any sibling billing tool.

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.