Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Prepaid/accrual amortisation schedule

accounting-schedules_accrual-prepaid-schedule
Read-onlyIdempotent

Spread a prepaid or accrual amount over months on a daily or equal-month basis with balancing journal entries. Price $0.02 USDC. POST /api/v1/accounting-schedules/accrual-prepaid-schedule. 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": {
      "amount": "<amount>",
      "start": "<start>",
      "end": "<end>",
      "accounts": "<accounts>"
    },
    "name": "accounting-schedules_accrual-prepaid-schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesstart, string, date. Required.
basisNobasis, string, one of daily, monthly_equal. Required.daily
startYesstart, string, date. Required.
amountYesamount, integer, from any to 9007199254740991. Required.
accountsYesaccounts, object. Required.

Output Schema

NameRequiredDescriptionDefault
entriesNoentries. Array.
periodsNoperiods. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered; the description adds genuinely new context by stating the $0.02 USDC price and that an unpaid call returns x402 payment terms without running. That payment-gate behavior is invisible from annotations and schema and is exactly what an agent needs to know. Minor ambiguity remains around whether the 'balancing journal entries' are merely returned in the response or persisted, which sits slightly at odds with readOnlyHint.

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?

Three short sentences with zero filler: capability first, then price and endpoint, then the payment-gate caveat. Everything is front-loaded and every sentence carries decision-relevant 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?

An output schema exists, so return values need not be described, and the description covers capability, cost, transport, and failure mode. It would be stronger if it mentioned the account-mapping requirement or date-ordering constraints, but for a five-parameter financial calculation endpoint 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 baseline is 3. The description does explain the amortisation basis concept behind the 'basis' enum (daily vs equal-month), which adds a little meaning, but it says nothing about the accounts object shape, amount constraints, or date-range rules beyond what the schema already declares.

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 first sentence names a specific verb and resource ('Spread a prepaid or accrual amount over months on a daily or equal-month basis with balancing journal entries') and the scope distinguishes it from depreciation, lease, and revenue-recognition siblings by domain. It stops short of explicitly naming which sibling to pick instead, so it is clear but not fully differentiated.

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 words 'prepaid or accrual' — an agent can infer this is the right tool for prepaid expense amortisation, but there is no explicit when-to-use/when-not statement or named alternative (e.g. versus loan-amortization-journal). The payment precondition is stated but that is a gating rule, not selection guidance.

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