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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

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.7/5.0
Disambiguation2/5

Multiple tools share overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, and the five polymarket_* tools cover heavily overlapping territory. An agent must read lengthy descriptions to distinguish between them, and pairs like validate_claim vs ask_pipeworx_grounded or discover_tools vs suggest_questions have fuzzy boundaries.

Naming Consistency2/5

Naming is wildly inconsistent: verb_noun (compare_entities, discover_tools), bare verbs (forget, remember, subscribe), noun phrases (entity_profile, recent_alerts, pipeworx_feedback), prefixed families (tradier_*, polymarket_*) and suffixed variants (ask_pipeworx_beta, ask_pipeworx_grounded). There is no single predictable convention across the set.

Tool Count2/5

34 tools is far beyond the 15-25 heavy range, and the count is inflated by near-duplicates like ask_pipeworx/ask_pipeworx_beta and five polymarket edge tools. The server mixes several unrelated domains (Tradier quotes/options, Pipeworx research, Polymarket analysis, memory, subscriptions, web utilities), making the scope feel unbounded.

Completeness2/5

For a server named Tradier, having only quote and option-chain endpoints is a significant gap—no historical data, account, positions, or order execution. The Pipeworx/Polymarket side is more complete, but the inclusion of unrelated utilities like generate_llms_txt and scan_dependency means no single domain is fully served.

Resources