Skip to main content
Glama

Actual 365 Interest Accrual

bpj_actual_365_interest_accrual
Read-onlyIdempotent

Accrue simple interest on an Actual/365 fixed basis over the provided number of days.

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": {
      "principal": "<principal>",
      "nominal": "<nominal>",
      "days": "<days>"
    },
    "name": "bpj_actual_365_interest_accrual"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
nominalYes
principalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered and the description does not need to repeat it. What the description does add beyond annotations is the computational basis (simple, not compound; Actual/365, not 30/360), which is genuinely useful. It omits rounding/precision handling and what the returned figure represents — the two things most likely to cause an incorrect downstream result in a financial accrual.

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 with no filler, front-loading the calculation method ahead of the input. Every clause (simple, Actual/365 fixed, provided days) carries information the agent needs.

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?

Three required numeric parameters and no output schema mean the description is the only place to explain what comes back and at what precision, and it is silent on both. The method and convention are well covered, so the definition is usable, but a financial calculation tool should state rounding treatment and the shape of the result.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%; only bare titles ('Nominal annual rate (%)', 'Principal', 'Actual days outstanding') and numeric bounds carry meaning, so the description must compensate and largely does not. It clarifies the day-count convention used to interpret 'days', which is valuable, but says nothing about the nominal rate being a percentage rather than a decimal, nothing about principal currency, and nothing about how the three combine.

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?

States a specific verb (accrue) plus the exact calculation method (simple interest, Actual/365 fixed) and the driving input (days), so an agent can tell instantly what computation this performs. It does not differentiate itself from any sibling, though the sibling list is a broad heterogeneous calculator catalog rather than a set of competing day-count conventions.

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 basis implicitly tells the agent when this applies (Actual/365 fixed-income accrual), but there is no explicit when-to-use, no mention of alternate day-count conventions or when to prefer them, and no prerequisites or constraints called out. Selection guidance is inferable from the name and basis 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.