plaid-mcp

list_linked_institutions_tool

List all linked financial institutions with account counts and error statuses. Reads Plaid-linked data from the local SQLite store.

Instructions

List every institution currently linked, with account counts and any errors.

Plaid-only — reads the local SQLite items table, which Teller doesn't use.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It explicitly says 'reads', indicating a read-only operation with no side effects, and describes the data source (local SQLite items table). It does not mention side effects or costs, but for a read tool this is sufficient.

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?

The description is two sentences: one for purpose and one for context. There is no redundancy or extraneous detail, making it appropriately concise.

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?

The description provides enough context for usage: what it does, the data source, and the Plaid scope. The output schema is present (not shown but indicated), so details about return values are covered there. It could mention what constitutes an 'institution' but that is not critical.

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

Parameters5/5

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

The input schema has no parameters (properties empty), so there is nothing to describe. The description accurately reflects that it lists all institutions without filters, making parameter explanations unnecessary.

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 clearly states the verb 'List' and the resource 'every institution currently linked', with account counts and errors. It also distinguishes itself by noting it is Plaid-only, which sets it apart from sibling 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?

The description gives a clear 'when to use' by stating it is Plaid-only and reads the local SQLite items table, implying it is appropriate for Plaid-linked institutions. It does not explicitly name alternatives but the scope is understood from the Plaid-versus-Teller context.

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