Skip to main content
Glama
Sign In
sophtron-mcp

sophtron-mcp

by 312-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Bank Connections

list_connections
Read-only

Retrieve all linked bank connections (UserInstitutions) for your account. Use this to review or manage connected financial institutions.

Instructions

List all linked bank connections (UserInstitutions) for this account.

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_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description's 'list all linked' wording is consistent with that. It adds the 'for this account' scoping detail, which is useful, but it does not mention pagination, ordering, or what happens when no connections exist.

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 a single, well-structured sentence with no filler. The key action and resource are front-loaded, and the parenthetical clarification is placed where it adds value without bloating the text.

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?

For a parameterless list tool with a readOnlyHint annotation, the description covers the essential purpose and scope. It lacks explicit usage guidance or output shape details, but the tool is simple enough that these are not critical gaps.

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?

There are zero parameters, so the description does not need to explain parameter behavior. The mention of 'for this account' provides meaningful context even without parameters, making the tool's execution context clear.

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 uses the specific verb 'list' with the resource 'bank connections' and clarifies the domain term 'UserInstitutions' in parentheses. It also specifies scope with 'for this account,' making it distinguishable from sibling tools like list_accounts or get_connection_accounts.

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

Usage Guidelines2/5

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

The description gives no guidance on when to choose this tool over alternatives such as search_institutions, create_connection, or get_connection_accounts. The intended use is only implied by the title and description, with no explicit context or exclusions.

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