Skip to main content
Glama

Complex Portal

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 indicate safe read-only, idempotent, open-world. Description adds rich detail: pulls specific financial data (revenue, net income, cash, debt) from EDGAR/XBRL with off-calendar handling, and for drugs FAERS counts, FDA approvals, trial counts. Notes sorting by primary metric and returns paired data + 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 dense but efficient; every sentence adds value. Front-loaded with examples and usage guidance. Slightly verbose but not wasteful. Could be trimmed marginally, but structure is logical.

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 no output schema and two entity types with different data sources, description is highly complete. Covers what data is returned per type, sorting, citation URIs, and efficiency gains. No gaps for agent to guess.

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%. Description adds meaning beyond schema: explains that type='company' pulls latest 10-K data, type='drug' pulls adverse-event/trial data; values examples show tickers vs drug names, constraints on array size. Provides concrete context for parameter use.

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?

Description clearly states the tool performs side-by-side comparison of 2–5 companies or drugs, with numerous example queries. Distinguishes from sequential single-pack lookups. Specific verb+resource: compare entities.

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 says 'ALWAYS PREFER over sequential single-pack lookups when comparing entities.' Provides clear context for when to use and examples of queries that trigger this tool.

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

All Complex Portal 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
Disambiguation2/5

Multiple tools have overlapping boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical, ask_pipeworx_grounded and deep_research heavily overlap with them, and entity_profile, compare_entities, recent_changes, and validate_claim all circle the same company-data space. The prediction-market cluster (polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread) also requires careful reading to distinguish. The descriptions help, but the set relies on them to disambiguate near-duplicates.

Naming Consistency4/5

Nearly all tools follow a consistent lowercase snake_case style, whether verb_noun (search_complexes, validate_claim, unsubscribe), noun_verb (entity_profile, recent_changes), or brand-like (ask_pipeworx, polymarket_edges). There is no camelCase mixing or chaotic verb style. Minor inconsistency exists between imperative verbs (remember, forget, subscribe) and noun-style names, but the overall pattern is readable and predictable.

Tool Count2/5

33 tools is well above the 25-tool 'heavy' threshold, and many are meta-tools (discover_tools, suggest_questions, pipeworx_feedback, pipeworx_trending, remember/recall/forget) that pad the surface. The server is named 'Complex Portal', yet only two tools serve that purpose—the rest belong to a broad data platform. The count feels inflated and misaligned with the server's stated identity.

Completeness3/5

For the broad Pipeworx data platform the surface is fairly complete: universal querying, grounded answers, deep research, entity profiles, comparisons, claim validation, subscriptions, memory, and feedback. For the Complex Portal domain named by the server, coverage is thin—just search and fetch-by-accession, with no browsing, species filtering, or cross-reference tools. The core workflow works, but the namesake domain is under-served relative to the rest of the set.

Resources