Skip to main content
Glama

schwab-mcp

by io.github.lonniev
OverviewDiscussionsAdmin

schwab_search_instruments

Search Schwab's instrument catalog by symbol, name, or CUSIP.

Returns up to 25 results in a markdown list (capped server-side here; Schwab itself may return more). A truncation footnote appears when the full result set exceeded 25.

Each row carries: symbol, asset type, description, optional exchange, optional CUSIP, and — when projection="fundamental" — P/E, dividend yield, and market cap in $B or $M.

  • () — [] CUSIP: | P/E:N.N | Yield:N.NN% | MktCap:$XB

Projection options (Schwab's API enum — determines how the search term is interpreted, not just what fields come back):

  • symbol-search: exact match on symbol (default; cheapest call).

  • symbol-regex: regex match against symbols. The pattern is regex, not a glob — "AAP.*" matches AAPL, AAP, etc.

  • desc-search: full-text match against the instrument description ("Apple", "semiconductor").

  • desc-regex: regex against descriptions.

  • fundamental: fetch fundamentals (P/E, yield, market cap) for a specific symbol. Use this when you already know the ticker and want the numbers, not a search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npubNoRequired. Your Nostr public key (npub1...) for credit billing.
symbolYesSearch term — ticker, regex, partial name, or CUSIP. The interpretation depends on `projection`.
dpop_tokenNo
projectionNo"symbol-search", "symbol-regex", "desc-search", "desc-regex", or "fundamental".symbol-search

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description bears the full burden. It discloses the result cap (25), truncation footnote, output format, and projection interpretation. It lacks explicit safety statements (e.g., idempotency) but implies read-only search.

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 well-structured: a summary sentence, then details on limits, output format, and projections. It uses markdown and bullet points efficiently, with no 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?

Given the presence of an output schema, the description provides comprehensive coverage of search behavior, result limits, and projection options. It could mention the no-result case, but overall it is complete for the tool's complexity.

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?

Schema description coverage is 75% (three of four parameters described). The description adds significant meaning for `symbol` and `projection`, explaining interpretation and examples. The undocumented `dpop_token` is minor with a default.

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 'Search Schwab's instrument catalog by symbol, name, or CUSIP,' specifying the resource and action. It distinguishes the tool from many siblings that deal with accounts, orders, or other functions.

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 provides explicit guidance on when to use each projection (symbol-search, symbol-regex, etc.), including cost implications. It does not explicitly exclude alternatives, but the context makes it clear that this is the search tool, and siblings are mostly non-search.

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

All schwab-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources