Skip to main content
Glama

BRAINIAC Consumer Credit & Deposit Disclosures

Regulation DD APY

consumer-credit_apy-calculate
Read-onlyIdempotent

Compute annual percentage yield for US deposit disclosures under Reg DD Appendix A, including stepped and tiered rates. Price $0.02 USDC. POST /api/v1/consumer-credit/apy-calculate. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "consumer-credit_apy-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNomode, string. Optional.
stepsNosteps, array. Optional.
tiersNotiers, array. Optional.
methodNomethod, string. Optional.
interestNointerest, integer. Optional.
principalNoprincipal, integer. Optional.
yearBasisNoyearBasis, value. Optional.
daysInTermNodaysInTerm, integer. Optional.
compoundingNocompounding, string. Optional.
assumedMaxBalanceNoassumedMaxBalance, integer. Optional.

Output Schema

NameRequiredDescriptionDefault
apyNoapy. Number.
sourcesNosources. Array.
apyExactNoapyExact. Number.
interestNointerest. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world. The description adds genuinely non-inferable behavior: a $0.02 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms instead of executing. It does not describe rate limits or the payment flow's completion path.

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, purpose first, then cost, then endpoint and failure mode. Every sentence carries information; the raw URL path is the least valuable element but is still relevant to agents invoking via HTTP.

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?

An output schema exists, so return values need no explanation, and payment behavior is covered. However, with 10 all-optional parameters and multiple conceptual modes, the description never explains which parameters are required for a stepped vs. tiered vs. simple calculation, leaving the agent to guess a valid call shape.

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 coverage is nominally 100%, so baseline is 3, but the schema descriptions are pure boilerplate ('mode, string. Optional.'). The description's mention of 'stepped and tiered rates' only loosely gestures at the steps/tiers parameters and adds no meaning for mode, method, yearBasis, compounding, or assumedMaxBalance.

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 and resource ('Compute annual percentage yield') plus the governing framework (Reg DD Appendix A) and scope ('US deposit disclosures', stepped and tiered rates). This implicitly separates it from the Reg Z APR sibling, though it never names other tools.

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 regulatory framing ('US deposit disclosures under Reg DD Appendix A') implies the domain where this applies, but there is no explicit when-to-use vs. the Reg Z APR or UK early settlement siblings, and no guidance on which mode or parameter combination to pick.

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