Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Fixed-rate loan amortisation journal

accounting-schedules_loan-amortization-journal
Read-onlyIdempotent

Compute a level-payment amortisation table and balancing journal entries for a fixed-rate loan. Price $0.03 USDC. POST /api/v1/accounting-schedules/loan-amortization-journal. An unpaid call returns the x402 payment terms and does not run.

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>",
      "annualRate": "<annualRate>",
      "termMonths": "<termMonths>",
      "firstPaymentDate": "<firstPaymentDate>",
      "accounts": "<accounts>"
    },
    "name": "accounting-schedules_loan-amortization-journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountsYesaccounts, object. Required.
principalYesprincipal, integer, from any to 9007199254740991. Required.
annualRateYesannualRate, number, from 0 to 1. Required.
termMonthsYestermMonths, integer, from any to 600. Required.
firstPaymentDateYesfirstPaymentDate, string, date. Required.

Output Schema

NameRequiredDescriptionDefault
rowsNorows. Array.
entriesNoentries. Array.
paymentNopayment. Number.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds real value beyond the annotations: the $0.03 USDC price, the POST endpoint, and the failure mode that an unpaid call returns x402 payment terms without running. However, it says nothing about computational conventions an accountant would care about (rounding, day-count, how the balancing entries are derived), which is the substance an agent cannot get from readOnlyHint/idempotentHint.

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?

Three short sentences, front-loaded with the core computation, then commercial terms, then failure behaviour. Efficient, though the endpoint path largely restates the tool name and the pricing sentence is more boilerplate than tool-specific information.

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?

With an output schema present, return values need no explanation, and all five required parameters are documented in the schema. What remains thin is the computational contract — rounding and entry-construction rules — but for a pure function with a defined output schema this is close to complete.

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 100%, so the schema already documents all five parameters and the nested accounts object. The description adds no parameter-level meaning at all — no clarification of the annualRate-as-decimal-fraction convention, the firstPaymentDate semantics, or how the loan/interest/cash accounts are consumed. Baseline 3 applies.

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 uses a specific verb+resource: 'Compute a level-payment amortisation table and balancing journal entries for a fixed-rate loan.' That is clearly distinct from siblings such as lease-schedule or depreciation-schedule by domain, but it never explicitly names or contrasts an alternative, 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 by the resource itself: you call this when you need an amortisation schedule plus journal entries for a level-payment fixed-rate loan. There is no explicit when-not guidance, no mention of what to use for floating-rate or non-level-payment loans, and no stated prerequisites beyond the payment note.

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.

Resources