Skip to main content
Glama

Tradier

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate mutation (readOnlyHint=false) and idempotency (idempotentHint=true). Description adds key behavioral details: scoped by identifier, persistence (24h for anonymous users). No contradictions.

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?

Five sentences, front-loaded with purpose. Every sentence adds value (when to use, how storage works, pairing with other tools). No fluff.

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 simple parameters (key, value) and no output schema, the description fully covers storage, retrieval, deletion, scoping, and persistence. No gaps.

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 coverage is 100%, so baseline 3. Description enriches with usage context (key as identifier like 'subject_property', value as findings) beyond schema labels, justifying a higher score.

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 saves data for reuse across conversations/sessions and gives concrete examples (resolved ticker, target address). It distinguishes from siblings like recall and forget.

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?

Explicitly says when to use ('when you discover something worth carrying forward') and mentions pairing with recall/forget. Lacks explicit 'do not use' scenarios but context is clear.

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