Skip to main content
Glama
Sign In
fintable-mcp

fintable-mcp

by jasoncbraatz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fintable_sync_accounts

Idempotent

Triggers a Plaid sync to fetch latest transactions and balances from all connected bank accounts.

Instructions

Trigger a sync of all connected bank accounts via Plaid.

This fetches the latest transactions and balances from your connected banks.

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": {
      "params": "<params>"
    },
    "name": "fintable_sync_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate the tool is not read-only, not destructive, idempotent, and open-world. The description adds that it fetches transactions and balances, which implies data modification, but does not elaborate on side effects, duration, or state changes beyond what annotations convey.

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 consists of two sentences. The first sentence states the primary action, and the second adds detail. Every word contributes value with no redundancy or filler.

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?

Given the tool is a simple sync trigger with an output schema, the description adequately covers the purpose and what is fetched. It could optionally mention that syncing might take time, but the current level is sufficient for an agent to understand the tool.

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

Parameters4/5

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

The input schema has a single required parameter 'params' which is an empty object. Since there are no meaningful parameters, the description's lack of parameter detail is acceptable. The baseline is raised because schema coverage is low but there is nothing to cover.

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 it triggers a sync of all connected bank accounts via Plaid, fetching latest transactions and balances. The verb 'sync' combined with 'accounts' matches the tool name and distinguishes it from sibling tools like 'list_accounts' (read-only) and 'resync_spreadsheets' (different resource).

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 indicates when to use the tool (to sync bank accounts) but does not provide explicit when-not-to-use or alternatives. Sibling tools exist for listing and resyncing spreadsheets, but no direct comparison or exclusion criteria are given.

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

Deploy Server

Other Tools