Skip to main content
Glama

Units of Production Depreciation

bpj_production_based_depreciation
Read-onlyIdempotent

Allocate the depreciable basis according to period output as a share of expected lifetime units.

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>",
      "output": "<output>",
      "lifetime": "<lifetime>"
    },
    "name": "bpj_production_based_depreciation"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes
outputYes
salvageYes
lifetimeYes

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 readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, which is appropriate for a pure calculation. The description adds the conceptual calculation but says nothing about the returned depreciation amount, rounding, or units, so it adds only limited behavioral context beyond the annotations.

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 single sentence is front-loaded, precise, and free of unnecessary wording. It communicates the core calculation without filler.

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 simple four-parameter pure calculator, the description covers the computation concept. However, with no output schema, it should ideally state what the tool returns (period depreciation expense) and any rounding or unit assumptions.

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. It maps domain concepts reasonably well through 'depreciable basis,' 'period output,' and 'expected lifetime units,' but it does not explicitly explain the formula, define depreciable basis as cost minus salvage, or clarify each parameter beyond the schema titles.

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 ('Allocate') and resource ('depreciable basis') and makes the units-of-production method clear through 'period output as a share of expected lifetime units.' This implicitly distinguishes it from straight-line depreciation, but it never names the sibling alternative explicitly, so it stops short of a 5.

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: an agent can infer this is the units-of-production depreciation method. The description gives no explicit when-to-use guidance, no exclusions, and does not mention when to choose straight-line depreciation instead.

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.