Skip to main content
Glama
Sign In
Public.com MCP Server

Public.com MCP Server

Official
by PublicDotCom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_all_instruments

Read-only

Retrieve all tradeable instruments with optional filters by type or trading status. Use to identify assets available for trading.

Instructions

List all available tradeable instruments with optional filters.

Args: type_filter: Filter by instrument types (e.g. ["EQUITY", "CRYPTO"]). Valid: EQUITY, CRYPTO, OPTION, ALT, BOND, INDEX, TREASURY, EVENTCONTRACT. trading_filter: Filter by trading status (e.g. ["BUY_AND_SELL"]). Valid: BUY_AND_SELL, LIQUIDATION_ONLY, DISABLED. account_id: Account ID. Optional if PUBLIC_COM_ACCOUNT_ID is set.

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": "get_all_instruments"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo
type_filterNo
trading_filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds valid filter values and the account_id environment fallback, but does not disclose pagination, rate limits, or default result size beyond what annotations imply.

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?

Front-loaded purpose sentence followed by a concise Args block that lists only necessary parameter details. No filler or repetition; the structure is appropriate for a tool with three undocumented parameters.

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 list/filter complexity and empty schema descriptions, the description covers purpose and all parameters adequately. It omits default behavior when filters are absent (return all instruments) and any pagination details, but the output schema presumably documents the return shape.

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

Parameters5/5

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

Schema coverage is 0%, so the description must document all three parameters, and it does: type_filter and trading_filter include exhaustive valid value lists, and account_id explains its optionality and env fallback. This fully compensates for the empty schema descriptions.

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?

Clearly states the verb 'List' and resource 'all available tradeable instruments', and the scope 'with optional filters'. It implicitly distinguishes from the singular sibling get_instrument by emphasizing 'all', though it does not name the alternative explicitly.

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?

Provides valid filter values and notes that account_id is optional if PUBLIC_COM_ACCOUNT_ID is set, which is useful setup context. However, it does not say when to choose this tool over get_instrument or how it relates to other listing/search tools, so guidance is incomplete.

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