Skip to main content
Glama

Absence Cover Cost

bpj_absence_cover_cost
Read-onlyIdempotent

Model temporary cover expense and forgone contribution for unstaffed hours to quantify the combined absence impact.

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": {
      "absent": "<absent>",
      "covered": "<covered>",
      "temp": "<temp>",
      "lost": "<lost>"
    },
    "name": "bpj_absence_cover_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
lostYes
tempYes
absentYes
coveredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, closed-world calculation, so the safety profile is covered. The description adds that the calculation combines temporary cover expense with forgone contribution for unstaffed hours, but it does not disclose the actual formula, assumptions, or output shape, which are the key behavioral traits for a model.

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. It presents the modeled components before the intended outcome, making it easy to scan.

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 four-parameter calculation with no output schema, the description should explain what is returned (separate cost components versus a combined figure) and the relationships among the inputs. It communicates the high-level purpose but leaves the computational output and formula unspecified, which limits an agent's ability to interpret results confidently.

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

Parameters4/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 the burden; it partially does by clarifying that lost contribution applies to "unstaffed hours," distinguishing it from the temp-covered portion. The parameter titles already convey units and meanings, but the description does not state how "covered" percentage interacts with "absent" hours to produce each component.

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 action ("Model") and two concrete outputs (temporary cover expense and forgone contribution) for a defined scope (unstaffed hours). It is clearly distinct from the many sibling cost calculators by its absence-cover focus, though it does not explicitly name an alternative.

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?

The stated purpose ("quantify the combined absence impact") implies when the tool applies, but there is no explicit when-to-use/when-not-to-use guidance or comparison to related cost tools. The usage context is inferable rather than stated.

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.