Skip to main content
Glama

BRAINIAC Consumer Credit & Deposit Disclosures

Regulation Z APR (Appendix J)

consumer-credit_reg-z-apr
Read-onlyIdempotent

Compute the US closed-end credit APR with the Reg Z Appendix J actuarial method and optional disclosure tolerance check. Price $0.04 USDC. POST /api/v1/consumer-credit/reg-z-apr. 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": {
      "payments": "<payments>"
    },
    "name": "consumer-credit_reg-z-apr"
  }
}

Input Schema

NameRequiredDescriptionDefault
advancesNoadvances, array. Optional.
paymentsYespayments, value. Required.
advanceDateNoadvanceDate, string. Optional.
disclosedAprNodisclosedApr, number, from 0 to 10. Optional.
amountFinancedNoamountFinanced, integer, from 1 to 9007199254740991. Optional.

Output Schema

NameRequiredDescriptionDefault
aprNoapr. Number.
sourcesNosources. Array.
aprExactNoaprExact. Number.
toleranceNotolerance. Number.
unitPeriodNounitPeriod. String.
firstPeriodNofirstPeriod. Object.
limitationsNolimitations. Array.
withinToleranceNowithinTolerance. Boolean.
unitPeriodsPerYearNounitPeriodsPerYear. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the price ($0.04 USDC), the POST endpoint, and the critical behavior that an unpaid call returns x402 payment terms and does not execute — a non-obvious trait an agent must know before calling. It stops short of describing tolerance-check outcomes (e.g., pass/fail semantics) or what the result contains, which the output schema presumably covers.

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, front-loaded with the core computation, followed by price/endpoint and the payment-gate behavior. Every sentence carries distinct, actionable information with no redundancy.

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 paid, read-only computation tool with full schema coverage, annotations, and an output schema, this is nearly complete: method, cost, endpoint, and the unpaid-call fallback are all covered. The remaining gap is the semantics of the tolerance result, which the output schema is expected to carry.

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 100%, so the baseline is 3; the description adds genuine meaning by linking 'optional disclosure tolerance check' to the disclosedApr input, telling the agent that supplying it triggers validation rather than just being another field. It does not clarify advances vs. advanceDate or the two payment shapes, but the schema documents those.

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 — 'Compute the US closed-end credit APR' — plus the governing method ('Reg Z Appendix J actuarial method') and the optional tolerance check. This distinguishes it from the APY calculator and other consumer-credit siblings without requiring schema inspection.

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 implied by the domain specificity (closed-end credit, Reg Z Appendix J), and the optional tolerance check hints at the validation use case. However, no explicit when-to-use/when-not guidance or named alternatives are given, leaving the agent to infer selection from the domain wording 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.

Resources