Skip to main content
Glama

BRAINIAC Consumer Credit & Deposit Disclosures

Regulation F call-frequency check

consumer-credit_reg-f-call-frequency
Read-onlyIdempotent

Check a debt-collector call log against the Reg F 7-in-7 presumption per debt. Price $0.02 USDC. POST /api/v1/consumer-credit/reg-f-call-frequency. 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": {
      "debtId": "<debtId>",
      "calls": "<calls>"
    },
    "name": "consumer-credit_reg-f-call-frequency"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsYescalls, array. Required.
debtIdYesdebtId, string, length 1 to 120. Required.
timezoneNotimezone, string, length 1 to 64. Required.America/New_York

Output Schema

NameRequiredDescriptionDefault
debtIdNodebtId. String.
sourcesNosources. Array.
violationsNoviolations. Array.
limitationsNolimitations. Array.
presumedViolationNopresumedViolation. Boolean.

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 declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description goes beyond them by disclosing the price ($0.02 USDC), the transport (POST /api/v1/...), and the paywall behavior that blocks execution — real operational context an agent needs before calling.

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 purpose and ending with the payment gate. Zero filler 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?

An output schema exists, so return values need no explanation, and all three parameters are fully specified. The pricing and paywall behavior are covered; only the specific 7-in-7 semantics (what counts as a violation) are left implicit, which is a minor gap for a domain-rule tool.

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 debtId, calls and timezone. The description only contributes the notion that checks are scoped "per debt," adding marginal meaning beyond the structured fields.

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 ("Check a debt-collector call log") plus the exact regulatory test applied ("Reg F 7-in-7 presumption per debt"). The purpose is unmistakable and cannot be confused with the sibling calculation 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?

Makes clear the tool is for evaluating a call log against the 7-in-7 presumption, and adds the crucial gate: an unpaid call returns x402 payment terms and does not execute. It stops short of naming when not to use it or pointing at alternatives, so not a 5.

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