Skip to main content
Glama

Project WIP Versus Billings

bpj_project_wip_billings
Read-onlyIdempotent

Estimate earned contract revenue under a cost-to-cost input method and compare it with cumulative billings.

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>",
      "actual": "<actual>",
      "scheduled": "<scheduled>",
      "bill": "<bill>"
    },
    "name": "bpj_project_wip_billings"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYes
actualYes
contractYes
scheduledYes

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world, so safety is covered. The description adds the valuation methodology, which is meaningful behavioral context, but it says nothing about the return shape (percent complete, over/under billing amount) despite having no output schema, and nothing about edge cases like final cost below actual cost.

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 front-loaded sentence with no filler, and the methodology and comparison are stated before any elaboration. It is efficient, though terse enough that one additional clause on the output or parameter mapping would have been better value than brevity.

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 read-only, four-required-number calculation, the description covers what is computed and the method, and annotations cover safety. The gap is that no output schema exists and the description does not indicate what the returned comparison looks like or how over/under billings are expressed, so an agent cannot fully predict results.

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 parameter meaning, and it only partially does: 'cost-to-cost input method' plus 'cumulative billings' explains how contract, actual, and scheduled costs combine into earned revenue. It never explicitly maps the four inputs, particularly that 'scheduled' means forecast final cost and that 'bill' is lifetime-cumulative, leaving that inference to the schema titles.

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 specific verb and resource ('Estimate earned contract revenue') plus the comparison being performed ('compare it with cumulative billings'), which is enough to distinguish it from a quote or NPV tool. It stops short of naming any sibling or stating how it differs from the adjacent project-finance tools, so it lands at 4 rather than 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 explicit when-to-use or when-not-to-use guidance. The 'cost-to-cost input method' phrase implicitly situates the tool in percentage-of-completion accounting, but the agent gets no signal about alternatives (e.g., fixed-fee quoting or commitment headroom) or prerequisites such as whether billings must be lifetime-cumulative.

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.