plaid-mcp

refresh_transactions_tool

Pull current transaction data from the bank via Plaid for a specific item. Use to update account activity.

Instructions

Nudge Plaid to pull fresh transactions from the bank right now.

Plaid-only.

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": "refresh_transactions_tool"
  }
}

Input Schema

Name	Required	Description	Default
`item_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations. The description hints at an action but does not disclose whether the refresh is synchronous, modifies stored data, has rate limits, or how failures are surfaced.

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?

Two short sentences with no filler or redundant wording.

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?

Even for a simple schema, the description omits item_id semantics, return/acknowledgment behavior, async vs sync execution, and error cases, so an agent cannot call it confidently.

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 only parameter, item_id, has no description in the schema or the tool description. Its optionality and default null are unexplained, leaving meaning entirely ambiguous.

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 the action (pull fresh transactions) and the context (Plaid, bank, immediate). Differentiates from get/search tools via the refresh intent, though 'nudge' is informal and 'Plaid-only' is vague.

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?

Only constraint is 'Plaid-only'. No explicit guidance on when to use this tool versus siblings like sync_transactions_tool, or when refresh is appropriate.

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