Skip to main content
Glama
Sign In
Schwab MCP

Schwab MCP

by JackGuan99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_accounts

Read-onlyIdempotent

Retrieve linked Schwab accounts with type, nickname, and key balances (total value, cash, buying power). Use the returned account labels in other tools.

Instructions

List the linked Schwab accounts with type, nickname and key balances (total value, cash, buying power). Use the returned account labels with the other tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description only adds a restatement of the returned fields, which the output schema also provides, so it contributes little behavioral context beyond the structured data.

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 short sentences with no filler; the purpose is front-loaded and the cross-tool hint follows immediately.

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?

With no parameters, an output schema present, and annotations covering the safety profile, the description is nearly sufficient. Only minor gaps remain, such as whether multiple accounts can be returned or whether authentication must already be established.

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 input parameters, so there is nothing for the description to disambiguate; baseline is 4. The description's mention of returned fields is output-side, not parameter-side.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the linked Schwab accounts') and enumerates the returned fields (type, nickname, total value, cash, buying power). It is naturally distinguishable from siblings like get_positions or get_portfolio_summary, but it never explicitly contrasts itself with them.

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 second sentence gives clear workflow context: use the returned `account` labels with the other tools, positioning this as the discovery/entry step. It does not name an alternative or state a when-not condition, so it stops short of a 5.

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