Skip to main content
Glama

BRAINIAC Consumer Credit & Deposit Disclosures

UK early settlement rebate

consumer-credit_uk-early-settlement
Read-onlyIdempotent

Compute the statutory minimum early-settlement rebate and settlement figure under the Consumer Credit (Early Settlement) Regulations 2004. Price $0.04 USDC. POST /api/v1/consumer-credit/uk-early-settlement. 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": {
      "advances": "<advances>",
      "repayments": "<repayments>",
      "apr": "<apr>"
    },
    "name": "consumer-credit_uk-early-settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
aprYesapr, number, from any to 10. Required.
advancesYesadvances, array. Required.
deferralNodeferral, string, one of none, one_month, 30_days. Required.none
repaymentsYesrepayments, value. Required.
periodBasisNoperiodBasis, string, one of month. Required.month
settlementDateNosettlementDate, string. Optional.
partialSettlementNopartialSettlement, boolean. Required.
treatLateAsOnTimeNotreatLateAsOnTime, boolean. Required.
lastPaidInstalmentNolastPaidInstalment, integer, from 0 to 1200. Optional.
noticeReceivedDateNonoticeReceivedDate, string. Optional.

Output Schema

NameRequiredDescriptionDefault
rebateNorebate. Number.
sourcesNosources. Array.
periodRateNoperiodRate. Number.
limitationsNolimitations. Array.
settlementDateNosettlementDate. String.
settlementFigureNosettlementFigure. Number.
fractionConventionNofractionConvention. String.
remainingRepaymentsTotalNoremainingRepaymentsTotal. Number.
outstandingAtLastInstalmentNooutstandingAtLastInstalment. 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?

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds important behavior beyond annotations: the $0.04 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms without running the calculation.

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?

The purpose is front-loaded, followed by price, endpoint, and payment behavior. Every sentence carries operational information and there is no redundant wording.

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 regulatory calculation with 10 parameters, an output schema, and full parameter coverage in the schema, the description is largely complete. It identifies the governing regulation and payment mechanics, though it could add more about calculation assumptions or scope.

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 parameters. The description adds no parameter-specific meaning beyond what the schema provides, such as how advances, repayments, deferral, or partial settlement affect the calculation.

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?

The description states a specific verb and resource: compute the statutory minimum early-settlement rebate and settlement figure under the Consumer Credit (Early Settlement) Regulations 2004. This is precise enough to distinguish it from sibling calculators such as APR, PMI, Reg F, and Reg Z tools.

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 description gives clear context for use and explains the payment-gated behavior for unpaid calls, which helps an agent understand when the tool will actually execute. It does not explicitly contrast this tool with the sibling calculators or state when another tool would be preferable.

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