Skip to main content
Glama

Overhead Absorption Variance

bpj_overhead_absorption_variance
Read-onlyIdempotent

Apply a predetermined overhead rate to actual activity hours and reconcile applied overhead to incurred overhead.

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": {
      "pool": "<pool>",
      "activity": "<activity>",
      "used": "<used>",
      "incurred": "<incurred>"
    },
    "name": "bpj_overhead_absorption_variance"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolYes
usedYes
activityYes
incurredYes

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 this as read-only, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds the calculation flow, but it does not disclose what is returned, how rounding or sign conventions are handled, or what happens in edge cases such as zero budgeted activity.

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?

The definition is a single front-loaded sentence with no filler. Every clause contributes to the stated computation, and there is no redundant repetition of the title or schema titles.

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 four required numeric parameters, 0% schema description coverage, and no output schema, the description should explain return values and parameter roles more fully. It states the core operation but leaves the result format, variance sign convention, and parameter semantics largely unspecified.

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 compensate for the lack of property descriptions. It implicitly links 'actual activity hours' to the used parameter, 'incurred overhead' to incurred, and a predetermined rate to pool divided by activity, but it never names the parameters or explains their units and constraints.

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 calculation: apply a predetermined overhead rate to actual activity hours and reconcile applied overhead to incurred overhead. It is clear enough to distinguish this as an overhead absorption variance computation, though it does not explicitly differentiate it from sibling variance tools.

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?

The description explains what the tool does but gives no guidance on when to use it versus alternatives such as bpj_pairs_weighted_variance or bpj_purchase_price_variance. There are no exclusions, prerequisites, or contextual triggers for selecting this tool.

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.