Skip to main content
Glama
Sign In
finance-mcp

finance-mcp

by adelaidasofia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

unlink

Revoke a linked institution's access by removing its Plaid connection and clearing stored data from keychain and local database.

Instructions

Remove a linked institution. Revokes the Plaid item, deletes the keychain entry, and clears local SQLite state.

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": {
      "institution_alias": "<institution_alias>"
    },
    "name": "unlink"
  }
}

Input Schema

NameRequiredDescriptionDefault
institution_aliasYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral consequences: revoking Plaid item, deleting keychain entry, and clearing local state. Clearly communicates destructive nature.

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 redundancy, front-loaded with verb and resource. Efficient and clear.

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?

Despite low complexity and presence of output schema, description omits parameter semantics and does not mention prerequisite (institution must be linked). Adequate but has clear gaps.

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?

Schema coverage is 0%, so description must explain parameter 'institution_alias'. It only states the parameter is required but gives no format, source, or example. Agent cannot infer where to get the alias value.

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?

Description clearly specifies the verb 'Remove a linked institution' and provides specific actions (revokes Plaid item, deletes keychain, clears SQLite). It distinguishes from sibling tools like link_start and sync_transactions.

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?

Description implies usage for unlinking an institution but lacks explicit guidance on when to use vs alternatives or prerequisites. No exclusion criteria or context about prior steps like linking.

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