Skip to main content
Glama

debtpulse

Analyze and strategize debt elimination with payoff calculators, creditor negotiation playbooks, settlement analysis, and consumer rights guides. Supports US, UK, AU, CA.

Instructions

DebtPulse: Global debt elimination intelligence. All endpoints require x402 payment (USDC on Base mainnet) via the PAYMENT-SIGNATURE header. Supports US, UK, Australia, and Canada jurisdictions. Add ?lang= for a

Coverage: Global

Endpoints: • payoff ($0.10): Payoff calculator • snapshot ($0.10): Debt burden snapshot • negotiate ($0.10): Creditor negotiation playbook • settle ($0.10): Debt settlement analysis • collections ($0.10): Debt collector rights • statute ($0.10): Statute of limitations lookup • garnishment ($0.10): Wage garnishment analysis • student ($0.10): Student loan strategy • credit ($0.10): Credit repair roadmap • build-credit ($0.10): Credit building strategy • dispute ($0.10): Credit dispute guide • insolvency ($0.10): Insolvency analysis • medical ($0.10): Medical bill negotiation • tax ($0.10): Tax debt relief • bnpl ($0.10): BNPL true cost analysis • payday ($0.10): Payday loan escape • mortgage-relief ($0.10): Mortgage relief options • consolidate ($0.10): Debt consolidation analysis • priority ($0.10): Multi-factor debt priority • rights ($0.10): Consumer debt rights • freedom-roadmap ($0.10): Debt freedom roadmap

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: payoff | snapshot | negotiate | settle | collections | statute | garnishment | student | credit | build-credit | dispute | insolvency | medical | tax | bnpl | payday | mortgage-relief | consolidate | priority | rights | freedom-roadmap
langNoResponse language code (en | es | fr | de | zh | hi | ar | pt | ja | ko | etc.)
debtsNoJSON array: [{creditor, balance, rate, minPayment}]
extra_paymentNoAdditional monthly payment amount in USD
methodNomethod
incomeNoMonthly income in USD
creditorNoCreditor name (e.g., Capital One, Chase, Midland Credit)
balanceNoCurrent balance in USD
months_behindNoNumber of months behind on payments
debt_typeNodebt_type
collectorNoCollection agency name
situationNosituation
stateNoUS state code (e.g., TX, CA)
provinceNoCA province or AU state code
last_paymentNoDate of last payment (YYYY-MM-DD) for expiry calculation
typeNotype
employer_typeNogovernment | nonprofit | private (for PSLF eligibility)
scoreNoscore
negativesNoComma-separated list of negative items
goalNogoal
goal_scoreNogoal_score
negative_itemsNonegative_items
bureauNobureau
assetsNoassets
bill_amountNobill_amount
insuranceNoinsurance
amount_owedNoamount_owed
years_behindNoyears_behind
platformNoplatform
payments_remainingNopayments_remaining
payment_amountNopayment_amount
fee_rateNoFee rate (e.g., '$15 per $100')
lenderNolender
servicerNoservicer
loan_typeNoConventional | FHA | VA | USDA
credit_scoreNocredit_score
homeownerNohomeowner
savingsNosavings
Behavior2/5

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

No annotations exist, so the description must disclose behaviors. It mentions x402 payment via header and supported countries, but does not explain consequences of missing payment, error cases, or return types. The lengthy endpoint list lacks behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose, cuts off mid-sentence ('Add ?lang= for a'), and uses a bullet list that is not fully integrated. It lacks clear structure and front-loading of key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 38 parameters, 21 actions, and no output schema, the description should provide more guidance on parameter usage per action. It does not explain what each endpoint returns or how to combine parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, many parameter descriptions are repetitive (e.g., 'method' -> 'method'). The tool description does not add meaning for most parameters; only the action enumeration is clarified via endpoint list. This fails to compensate for weak schema descriptions.

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?

The description states 'DebtPulse: Global debt elimination intelligence' and lists endpoints (e.g., payoff, snapshot), which clarifies it performs various debt-related analyses. However, it does not use a specific verb-resource structure and is somewhat scattered.

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 description mentions payment requirements and supported jurisdictions, which is helpful. However, it does not explicitly state when to use this tool versus siblings (e.g., taxpulse) or provide when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server