Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Unrealised FX revaluation

accounting-schedules_fx-revaluation
Read-onlyIdempotent

Revalue foreign-currency monetary balances at closing rates and propose unrealised gain/loss journal entries. Price $0.03 USDC. POST /api/v1/accounting-schedules/fx-revaluation. 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": {
      "functionalCurrency": "<functionalCurrency>",
      "balances": "<balances>",
      "closingRates": "<closingRates>",
      "rateQuote": "<rateQuote>"
    },
    "name": "accounting-schedules_fx-revaluation"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoasOf, string, date. Optional.
accountsNoaccounts, object. Required.
balancesYesbalances, array. Required.
rateQuoteYesrateQuote, string, one of foreign_per_functional, functional_per_foreign. Required.
closingRatesYesclosingRates, object. Required.
functionalCurrencyYesfunctionalCurrency, string, length 3 to 3. Required.

Output Schema

NameRequiredDescriptionDefault
linesNolines. Array.
entriesNoentries. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
totalGainLossNototalGainLoss. Number.
functionalCurrencyNofunctionalCurrency. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavior: the operation only *proposes* journal entries, costs $0.03 USDC, and is gated by x402 so an unpaid call is a no-op returning payment terms — none of which is in the annotations. It does not disclose failure modes, e.g. a balance currency missing from closingRates.

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 operation and outcome, then cost/payment, then the transport path. Little waste; the raw endpoint path is the only mildly redundant element given the tool name, though it aids direct HTTP use.

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 not be explained, and the description covers purpose, pricing, and the payment gate for a 6-parameter nested tool. What remains thin is the operational detail an agent would want — what a "proposed" entry looks like versus a posted one, and behavior when closing rates are incomplete.

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 carries the parameter burden and a 3 is the baseline. The description adds no parameter meaning at all — notably it does not clarify the ambiguous rateQuote direction (foreign_per_functional vs functional_per_foreign) or what accounts.gainLoss controls.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Revalue foreign-currency monetary balances at closing rates and propose unrealised gain/loss journal entries." That is precise enough to separate it from every sibling schedule tool (depreciation, lease, loan amortization, intercompany elimination) without them being named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening clause implies the trigger condition (foreign-currency monetary balances needing revaluation at closing rates) and the payment clause states a hard prerequisite: an unpaid call returns x402 terms and does not run. It stops short of explicit when-not-to-use or naming an alternative tool for related FX tasks.

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