Skip to main content
Glama

Critical Chain Buffer Use

bpj_critical_chain_buffer_use
Read-onlyIdempotent

Compare buffer consumption with critical-chain progress and extrapolate buffer use if the same consumption pace continues.

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": {
      "buffer": "<buffer>",
      "consumed": "<consumed>",
      "progress": "<progress>"
    },
    "name": "bpj_critical_chain_buffer_use"
  }
}

Input Schema

NameRequiredDescriptionDefault
bufferYes
consumedYes
progressYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that the projection assumes constant consumption pace — but says nothing about what the comparison yields (ratio, verdict, projected overrun) or how degenerate inputs 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?

A single tight sentence with the analytical action and its assumption front-loaded, and no filler whatsoever. Nothing could be removed without losing 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?

For a small three-number calculator this is thin: there is no output schema, and the description does not say what the extrapolated result looks like (e.g., buffer percentage consumed versus chain completion, or projected buffer at finish). An agent can pass the arguments but cannot predict or interpret the return value from the description alone.

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%, and the description never mentions the three inputs by name, unit, or format; it only obliquely references "buffer consumption" and "progress." The schema's titles do carry units (days, percent), but the free-text adds essentially no parameter meaning beyond that.

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 specific operations ("compare buffer consumption with critical-chain progress" and "extrapolate buffer use") on a specific resource, so an agent knows this is a buffer-burn analysis rather than a generic calculator. It does not differentiate itself from a related sibling like bpj_schedule_critical_path, but the verb+resource pairing is concrete enough to stand on its own.

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: the phrase "if the same consumption pace continues" hints at the linear-extrapolation premise, which is a use condition of sorts. There is no explicit statement of when to prefer this over a critical-path scheduling tool, no prerequisites, and no exclusions.

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.