Skip to main content
Glama

Capped Time and Materials Invoice

bpj_capped_time_material_invoice
Read-onlyIdempotent

Compare time and reimbursable material charges with the unused contract cap to determine invoiceable and excess amounts.

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": {
      "authorized": "<authorized>",
      "prior": "<prior>",
      "hours": "<hours>",
      "rate": "<rate>",
      "expenses": "<expenses>"
    },
    "name": "bpj_capped_time_material_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes
hoursYes
priorYes
expensesYes
authorizedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 the safety profile is fully covered and the bar is lower. The description adds genuine behavioral content beyond that: it reveals the operation splits results into invoiceable and excess amounts, which is the only source of return-shape information given there is no output schema. It stops short of stating rounding, currency, or what happens at the cap boundary.

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?

A single sentence with zero filler, front-loaded with the comparison and ending on the decision it produces. Nothing to cut and nothing out of order.

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?

This is a simple five-input arithmetic tool with no output schema, and the description covers both what is compared and what the result distinguishes, which is about the right level of detail. It is slightly thin on boundary behavior (exact treatment when charges meet or exceed the remaining cap) and on units or rounding, which matters for an invoicing calculation.

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

Parameters5/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 load. It does: 'time charges' maps to hours x rate, 'reimbursable material charges' maps to expenses, and critically 'unused contract cap' clarifies that the cap is the authorized amount net of the prior-billed parameter rather than the raw cap. That resolves the ambiguous 'prior' and 'authorized' pair that titles alone leave open. It does not spell out the arithmetic for every field, but no parameter is left semantically unresolved.

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 computation: comparing time and material charges against the unused contract cap to split invoiceable from excess amounts. That is a clear verb-and-resource statement an agent can act on. It does not name or distinguish itself from any sibling, and the sibling names are all unrelated calculators, so a 4 rather than a 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, when-not-to-use, or prerequisite guidance. The description only asserts what the tool computes; it never says under what circumstances an agent should choose this capped-invoice calculation over anything else, nor that the cap and prior billed amounts must already be known.

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.