Skip to main content
Glama

Contract Service Backlog

bpj_contract_service_backlog
Read-onlyIdempotent

Calculate delivered revenue and remaining performance obligation for a fixed contract fulfilled evenly by month.

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": {
      "commitment": "<commitment>",
      "length": "<length>",
      "delivered": "<delivered>"
    },
    "name": "bpj_contract_service_backlog"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthYes
deliveredYes
commitmentYes

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral fact — that fulfillment is assumed even across months — but says nothing about rounding/precision, currency, or what happens when delivered months exceed the contract term. With no output schema present, that missing return-side detail is a real gap.

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 front-loaded sentence with no filler; the verb, the two outputs, and the contractual assumption all land immediately. Nothing is repeated from the title or schema.

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 three-parameter, output-schema-less calculation tool, the definition names both return quantities, which is the most important completeness signal. However, it leaves boundary behavior (delivered = 0, delivered > length), numeric precision, and currency semantics unspecified, which an agent needs in order to trust and interpret the result.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema supplies only short titles ('Contract term months', 'Full months delivered', 'Total contract commitment') and constraints. The description's 'fulfilled evenly by month' hints at the pro-rata relationship between length and delivered, but it never clarifies units or currency for commitment, whether delivered is capped at length, or what result a delivered value exceeding length produces.

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 gives a specific verb ('Calculate') and names both computed quantities (delivered revenue and remaining performance obligation), plus the contract model that makes the math well-defined ('fixed contract fulfilled evenly by month'). It does not explicitly contrast itself with any sibling, but the sibling list contains no obviously adjacent revenue-recognition tool, so the purpose is still unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the purpose statement: an agent can infer this applies to straight-line, evenly-fulfilled contracts, but the description never states when to prefer this over another calculation or what preconditions must hold. There are no exclusions, no prerequisites, and no mention of what to do for non-even or usage-based contracts.

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.