Skip to main content
Glama

Schedule Crash Cost Slope

bpj_schedule_crash_cost_slope
Read-onlyIdempotent

Compare normal and crash duration and cost to estimate incremental direct cost per day shortened.

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": {
      "normalDays": "<normalDays>",
      "crashDays": "<crashDays>",
      "normal": "<normal>",
      "crash": "<crash>"
    },
    "name": "bpj_schedule_crash_cost_slope"
  }
}

Input Schema

NameRequiredDescriptionDefault
crashYes
normalYes
crashDaysYes
normalDaysYes

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, non-destructive, and closed-world, so the safety profile is covered. The description adds that the result is an estimate of incremental cost per day shortened, but says nothing about unit/currency, rounding, or what happens when crashDays equals or exceeds normalDays (a zero or negative denominator).

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. It is efficient, though the terseness leaves no room for the edge-case note that would materially help an agent.

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

Completeness4/5

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

For a small four-number calculator with no output schema, stating that the output is incremental direct cost per day shortened is largely sufficient. The main remaining gap is domain constraints on the inputs, such as crashDays being shorter than normalDays.

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 meaning; it does name all four inputs conceptually (normal/crash duration and cost), and the schema titles reinforce them. However, it adds no detail on units, allowable ranges, or the relationship constraint that crashDays should be less than normalDays.

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 verb and outcome: estimate the incremental direct cost per day shortened by comparing normal and crash duration/cost. That is concrete enough to distinguish it from generic cost tools, though it never names a sibling or routing rule.

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, no prerequisites, and no mention of alternatives among the many bpj_* cost tools. The intended context (schedule crashing analysis) is only implied by the phrase 'crash duration.'

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.