Skip to main content
Glama

Tradier

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A5/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description confirms read-only behavior (retrieve/list) and adds scoping info. No contradiction.

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?

Three concise sentences front-loaded with purpose. Every sentence adds value: core function, contextual usage, and relationship with siblings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool (one optional param, no output schema, rich annotations), the description fully covers usage, scoping, and sibling relationships. No gaps.

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 100% with a single optional key parameter. Description adds clear semantics: provide key to retrieve specific value, omit to list all keys. Goes beyond schema by explaining the dual behavior.

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 retrieves a value saved via remember or lists all keys. It distinguishes itself from siblings (remember, forget) by specifying the retrieval and listing behavior.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use (look up stored context without re-deriving) and how to use (omit key to list all). Mentions scoping and pairing with remember/forget, offering clear context and alternatives.

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

All Tradier toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and discover_tools all serve general data querying, while bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_edge_tracker all target prediction-market opportunities. An agent would struggle to pick the right one consistently despite long descriptions.

Naming Consistency2/5

Naming conventions are mixed: some tools use snake_case bare verbs (remember, recall, forget), some use a pipeworx_ prefix, some use tradier_ prefix, and some use descriptive phrases (generate_llms_txt, scan_competitor_ai_presence). There is no consistent verb_noun or prefix pattern across the set.

Tool Count2/5

34 tools is on the heavy side, but more importantly the count does not match the server's stated identity. The server is named Tradier, yet only 3 of 34 tools are Tradier-specific market data tools; the rest are Pipeworx research, prediction-market, memory, and subscription utilities. The scope feels bloated and unfocused.

Completeness1/5

For a server named Tradier, the surface is severely incomplete: only quote, option expirations, and option chain are provided. Missing are account info, positions, orders, historical data, watchlists, and other core brokerage/trading operations. The Pipeworx research side is broad, but the apparent trading domain has major gaps that would cause agent failures.

Resources