Skip to main content
Glama

Billable Capacity Contribution

bpj_billable_capacity_contribution
Read-onlyIdempotent

Apply client billing only to utilized hours while charging labor cost on all paid hours to estimate delivery contribution.

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": {
      "workload": "<workload>",
      "billable": "<billable>",
      "bill": "<bill>",
      "rate": "<rate>"
    },
    "name": "bpj_billable_capacity_contribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYes
rateYes
billableYes
workloadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. Beyond that the description adds the billing logic but not the output shape, the time basis of the result (weekly vs. annualized), or whether the contribution figure is a per-hour or per-period amount — material gaps for a pure calculator. It slightly conflicts in spirit with the read-only hint only in the sense that 'charging labor cost' reads as a write action, which could mislead an agent skimming the text.

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 tight sentence with no filler, and the billing rule is front-loaded before the outcome. It is dense but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no per-parameter descriptions, the description is the only source of truth, and it omits what is actually returned (a contribution amount? a margin?) and over what period. For a four-parameter required-input calculator, that omission is a real usability gap.

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%, so the description must carry parameter meaning. It does loosely map all four inputs — client billing rate, base hourly rate as labor cost, utilization percentage, and workload hours — but never names units or clarifies that utilization is a percentage applied to workload, leaving an agent to reconstruct the formula from prose.

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 sentence names the computation ('estimate delivery contribution') and spells out the mechanism: bill only utilized hours, charge labor on all paid hours. That is a specific verb+resource pairing an agent can distinguish from capacity siblings, though the phrasing leads with the formula fragment rather than a clean statement of purpose.

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 indication of when to reach for this tool versus the many sibling 'capacity' and 'contribution' calculators, no prerequisites, and no stated context (per-week? per-engagement?). The agent must infer applicability entirely from the formula.

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.