Skip to main content
Glama
BradMorphsters

tuskledger-mcp

run_sync

Sync all connected accounts with Plaid to fetch updated transactions and balances. Returns a summary of accounts updated and new transactions added.

Instructions

Trigger a Plaid sync across all connected items. Same as clicking 'Sync Now' in the UI. Returns a summary of what was fetched (accounts updated, transactions added). Safe to call freely — Plaid dedupes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Dispatch handler for the 'run_sync' tool. Calls client.trigger_sync() to perform a Plaid sync across all connected items.
    if name == "run_sync":
        return client.trigger_sync()
  • Tool definition for 'run_sync' with description and empty input schema (no parameters needed).
    Tool(
        name="run_sync",
        description=(
            "Trigger a Plaid sync across all connected items. Same as "
            "clicking 'Sync Now' in the UI. Returns a summary of what was "
            "fetched (accounts updated, transactions added). Safe to call "
            "freely — Plaid dedupes."
        ),
        inputSchema={"type": "object", "properties": {}, "additionalProperties": False},
    ),
  • Registration of the tool via @server.list_tools() which returns the TOOLS list containing the run_sync Tool instance.
        return TOOLS
    
    @server.call_tool()
  • The call_tool dispatcher routes the 'run_sync' name to _dispatch, which calls client.trigger_sync().
    @server.call_tool()
    async def call_tool(name: str, arguments: dict) -> list[TextContent]:
        log.info("tool call: %s args=%s", name, list((arguments or {}).keys()))
        try:
            # The HTTP calls are blocking; offload to a thread so we don't
            # stall the event loop. Backend is on localhost so latency is
            # tiny but doing this correctly keeps the door open for
            # async-aware tools later.
            payload = await asyncio.to_thread(_dispatch, name, arguments, cli)
  • Client helper method that sends a POST request to /api/plaid/sync, the underlying HTTP call triggered by the run_sync tool.
    def trigger_sync(self) -> Any:
        return self._request("POST", "/api/plaid/sync")
Behavior4/5

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

Without annotations, the description discloses the sync trigger, output summary, and safety due to deduplication. It doesn't mention rate limits or async behavior, but provides reasonable transparency for a simple action.

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 sentences, no wasted words. Front-loaded with the action verb and clear purpose.

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 zero parameters and no output schema, the description covers the essentials: trigger, return summary, and safety. Could mention sync duration but is sufficient.

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?

No parameters exist, per instructions baseline is 4. No additional parameter info needed since schema coverage is complete.

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 Plaid sync across all connected items, analogizes to UI Sync Now, and specifies the output summary. This distinguishes it from siblings which are all read-only query 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 implies usage for syncing data but doesn't explicitly state when to prefer this over alternatives. It does convey that calling is safe and deduplication occurs, giving some usage confidence.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BradMorphsters/tuskledger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server