plaid-mcp

add_external_debt_tool

Add an external debt not linked to a Plaid account to track its balance, APR, and payment details.

Instructions

Track a debt that isn't behind a linked Plaid account.

Plaid-only.

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": {
      "name": "<name>",
      "balance": "<balance>",
      "apr": "<apr>"
    },
    "name": "add_external_debt_tool"
  }
}

Input Schema

Name	Required	Description	Default
`apr`	Yes
`name`	Yes
`note`	No
`balance`	Yes
`promo_expires`	No
`minimum_payment`	No
`next_payment_due_date`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.1/5.0

Behavior1/5

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

The description gives no information about side effects, data modifications, authentication requirements, or whether this is a create operation. With no annotations, the description alone fails to disclose any behavioral implications of invoking this tool.

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 concise but overly sparse—two short sentences without structured details. It conveys minimal information and does not organize any usage context or parameter hints, failing to be usefully structured.

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

Completeness1/5

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

For a tool with seven parameters and three required fields, this description is severely incomplete. It lacks parameter explanations, usage scenarios, and any relationship to other tools, leaving the agent without sufficient context to use the tool correctly.

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

Parameters1/5

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

The description does not explain any of the seven parameters (name, balance, apr, etc.). The schema lacks descriptions, so the agent has no guidance on what each parameter means or how to fill them correctly.

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 that the tool tracks a debt not linked to a Plaid account, and the tool name 'add_external_debt_tool' clarifies it is for adding external debts. However, the phrasing 'isn't behind a linked Plaid account' is slightly awkward and could be clearer, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for non-Plaid debts but does not explicitly distinguish from sibling tools like 'link_account' or 'get_liabilities_tool'. No conditions, prerequisites, or when-not-to-use guidance is provided, leaving the agent to infer when this tool is appropriate.

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