plaid-mcp

sync_transactions_tool

Syncs new Plaid transactions into a local cache using incremental cursors, ensuring up-to-date data without duplicates.

Instructions

Pull the latest transactions from Plaid into the local cache. Idempotent and incremental — uses cursors from the last sync.

Plaid-only: Teller has no cursor-based sync; get_transactions_tool fetches Teller transactions live by date range.

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

Input Schema

Name	Required	Description	Default
`wait_for_ready`	No
`wait_timeout_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavioral traits: idempotent, incremental, cursor-based, and cache-writing. However, it does not explain side effects on the local cache, return behavior, error handling, or the effect of wait_for_ready/wait_timeout_seconds.

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 compact sentences are front-loaded with purpose, then behavior, then usage routing. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

For a sync tool with two optional parameters and no output schema, the description covers selection and invocation basics but omits return values, failure modes, and wait-parameter semantics. It is adequate, not complete.

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?

The schema has 0% description coverage and the description never mentions wait_for_ready or wait_timeout_seconds. The names and defaults hint at waiting behavior, but an agent cannot understand what 'ready' means or how the timeout is applied.

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 opens with a specific verb and resource: 'Pull the latest transactions from Plaid into the local cache.' It clearly identifies the source (Plaid) and differentiates from the sibling get_transactions_tool by stating 'Plaid-only' and contrasting Teller behavior.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: use this for Plaid cursor-based sync, and explicitly names get_transactions_tool as the alternative for Teller live date-range fetches. The idempotent/incremental note also tells agents this tool is safe to reuse.

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