Skip to main content
Glama

Traject Ecommerce

by io.github.pipeworx-io

Compare Entities

compare_entities
Read-onlyIdempotent

"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type: "company" or "drug".
valuesYesFor company: 2–5 tickers/CIKs (e.g., ["AAPL","MSFT"]). For drug: 2–5 names (e.g., ["ozempic","mounjaro"]).

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, open-world. Description adds details: pulls latest 10-K from SEC EDGAR/XBRL, handles off-calendar fiscal years, returns sorted by primary metric, includes citation URIs. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is front-loaded with triggers and key action, but longer than necessary. Every sentence adds value, though some redundancy could be trimmed. Still well-structured.

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?

Despite no output schema, the description explains return format (paired data + citation URIs, sorted by primary metric). Covers both entity types. Complete for a 2-param tool.

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% (both parameters described). Description adds meaning: explains 'type' enum values (company/drug) and 'values' format (tickers/CIKs for company, drug names). Also details data sources per type.

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 performs side-by-side comparisons of 2-5 companies or drugs, pulling specific financial data for companies and adverse-event/trial data for drugs. It distinguishes from sequential single-pack lookups by name.

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?

Explicitly lists natural language triggers ("compare X and Y", "X vs Y", etc.) and instructs to ALWAYS PREFER over sequential lookups when comparing entities.

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

All Traject Ecommerce 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.8/5.0
Disambiguation4/5

Most tools have distinct purposes, e.g., Amazon and Walmart tools are platform-specific. A few overlapping tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research are differentiated by clear usage guidance, so an agent can disambiguate with reasonable effort.

Naming Consistency3/5

Tool names mix verbs and nouns with varying styles (e.g., ai_visibility_check, compare_entities, scan_competitor_ai_presence). There is no uniform pattern like verb_noun; some are descriptive phrases. The inconsistency is noticeable but not chaotic.

Tool Count2/5

36 tools is too many for a server named 'Traject Ecommerce', as many tools cover unrelated domains (Polymarket, npm packages, SEC filings). The scope is excessively broad, making the server feel like a general-purpose plugin rather than a focused ecommerce toolset.

Completeness2/5

For an ecommerce-focused server, it only covers Amazon and Walmart product/search/reviews, missing major platforms and backend operations. The broader tool set is detailed but not ecommerce-specific, leaving obvious gaps for the intended purpose.

Resources