Skip to main content
Glama

Straight-Line Depreciation

bpj_straight_line_depreciation
Read-onlyIdempotent

Allocate depreciable cost evenly over full years and months after deducting residual value.

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": {
      "cost": "<cost>",
      "salvage": "<salvage>",
      "life": "<life>"
    },
    "name": "bpj_straight_line_depreciation"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes
lifeYes
salvageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety behavior is covered. The description adds genuine method context — residual value is deducted first and allocation is even across full years and months — but says nothing about what is returned (a single annual charge vs. a full period schedule).

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 front-loaded sentence with no filler; the deductible base and the allocation rule both appear before any qualifying detail.

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 small three-parameter pure calculation with no output schema, the definition explains the formula inputs but not the result shape, so an agent cannot tell whether it receives one annual figure or a per-period schedule. Adequate but with a real 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 carries the burden and partially does: it maps 'residual value' to the salvage parameter and frames cost minus salvage as the depreciable base, plus life as years. It leaves open the months-vs-integer-years ambiguity (life is an integer in years only) and gives no constraint that salvage must not exceed cost.

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 verb and resource ('allocate depreciable cost') and pins the method ('evenly over full years and months after deducting residual value'), which implicitly separates it from production-based depreciation. It stops short of naming or contrasting a sibling explicitly.

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 straight-line method is implied as the selection criterion, but there is no statement of when to prefer this over alternatives such as production-based depreciation, and no prerequisites or exclusions are given.

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.