Skip to main content
Glama
Sign In
sophtron-mcp

sophtron-mcp

by GraysonCAdams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Toggle Account Visibility

toggle_account

Control account visibility by showing or hiding a bank account in your active list. Specify user institution, account ID, and selection state to update its displayed status.

Instructions

Show or hide a bank account from the active list.

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": {
      "userInstitutionId": "<userInstitutionId>",
      "accountId": "<accountId>",
      "selected": "<selected>"
    },
    "name": "toggle_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectedYestrue to show, false to hide
accountIdYesAccount ID
userInstitutionIdYesUserInstitution ID

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 annotations declare readOnlyHint: false, indicating a write operation. The description adds that the operation affects the active list, but does not disclose persistence, permission requirements, or reversibility beyond this basic behavior. While the bar is lower due to annotations, the description provides minimal additional context.

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, front-loaded sentence with no redundant information. It achieves maximum efficiency by stating the core function and scope without wasted words.

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?

This is a simple tool with three well-documented parameters and no output schema. The description explains the core function and scope ('active list') sufficiently for an agent to select and invoke it. However, it does not mention return values or prerequisites, which is a minor gap given the low complexity.

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

Parameters3/5

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

Schema descriptions cover all three parameters comprehensively, including the semantics of 'selected' (true to show, false to hide). The description does not add parameter information beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 tool's function with a specific verb ('Show or hide') and resource ('a bank account from the active list'). It effectively distinguishes this tool from siblings like rename_account or save_account_preferences by focusing on visibility toggling.

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 implies the tool is for toggling visibility but does not explicitly state when to use it instead of alternatives such as save_account_preferences or rename_account. There is no mention of exclusions or when-not conditions, leaving usage somewhat implied.

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