Skip to main content
Glama

Borrowing Cost Capitalization

bpj_borrowing_cost_capitalization
Read-onlyIdempotent

Estimate avoidable interest from weighted expenditure, annual rate and eligible time, capped at actual period borrowing costs.

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": {
      "averageSpend": "<averageSpend>",
      "nominal": "<nominal>",
      "fraction": "<fraction>",
      "actualInterest": "<actualInterest>"
    },
    "name": "bpj_borrowing_cost_capitalization"
  }
}

Input Schema

NameRequiredDescriptionDefault
nominalYes
fractionYes
averageSpendYes
actualInterestYes

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 this a read-only, idempotent, non-destructive local computation, so safety behavior is fully covered elsewhere. The description's added value is the capping rule — the result cannot exceed actual period borrowing costs — which explains a real behavioral property of the output. It does not say whether the result is rounded, what happens if fraction is zero, or what form the response takes.

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 sentence that front-loads the operation, names the inputs in order, and ends with the binding constraint. No filler, no restatement of the name or title.

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 four-parameter, no-output-schema calculator, the description supplies the formula shape and the cap, which is enough to call it correctly. Minor gaps remain around return format and edge-case handling, but nothing an agent needs in order to invoke it is missing.

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 semantic load, and it does map each of the four parameters to its role: weighted expenditure, annual rate, eligible time, and actual period borrowing costs as the cap. Remaining ambiguity (units for fraction, currency of the monetary inputs) is partly resolved by the schema's own titles, but not by the description.

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 ('Estimate') and a specific financial quantity ('avoidable interest'), and lists the three inputs that drive it plus the cap rule, so an agent knows exactly what the tool computes. It stops short of distinguishing itself from near-domain siblings such as weighted capital cost or interest accrual tools, so it lands at 4 rather than 5.

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 guidance, no prerequisites, and no mention of alternatives or when not to use this tool. The accounting context (capitalized interest on qualifying assets) must be inferred from the description's vocabulary alone.

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.