Skip to main content
Glama

Currents

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"]).

Schema Changelog

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

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations indicating safety and idempotency, the description adds valuable behavioral details: handling off-calendar fiscal years, sorting by primary metric, and returning citation URIs. No contradictions with annotations.

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?

The description is front-loaded with trigger phrases and packs significant information without wasted words. It is slightly dense but every sentence earns its place.

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

Completeness4/5

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

Given no output schema, the description explains return values (paired data, citation URIs) and data sources. It could specify response format more precisely, but overall adequate for the tool's simplicity.

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%, but the description adds meaning by explaining data sources per type and providing example inputs, thus adding value beyond the schema.

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 uses specific verbs like 'compare' and 'side-by-side comparison,' clearly states the resource (companies or drugs), and distinguishes from sibling tools by explicitly preferring this over sequential single-pack lookups.

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?

The description provides clear context for when to use (comparing 2–5 entities) and explicitly prefers over sequential lookups. It does not explicitly mention alternatives for single-entity queries, but the sibling 'entity_profile' implies that.

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

All Currents 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

Several tool clusters are hard to tell apart: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers (beta currently behaves exactly like stable), and the six polymarket_* tools plus bet_research all overlap around edge and arbitrage discovery. The descriptions are detailed and help, but an agent must read carefully to avoid misselecting a sibling tool.

Naming Consistency3/5

Names are consistently lowercase snake_case, but the verb/noun ordering is mixed: verb-first names (ask_pipeworx, list_categories, resolve_entity) coexist with noun-first names (polymarket_edges, entity_profile, pipeworx_feedback, recent_alerts) and bare verbs (remember, recall, forget). Readable overall, but the pattern is not systematic.

Tool Count2/5

34 tools is well beyond the 25+ threshold and spans at least six loosely related domains (news, structured data research, prediction markets, AI visibility, memory, subscriptions), making the server feel like a multi-product grab bag. Meta-tools like discover_tools, suggest_questions, and pipeworx_trending add further navigation overhead.

Completeness4/5

Within each bundled domain the lifecycle is well covered: data lookup has routing, grounded mode, deep research, entity resolution, comparison, and claim validation; Polymarket has research, arbitrage, edge, fill-risk, and cross-venue spread tools; memory and subscriptions each have full CRUD-ish flows. Minor gaps like subscription updating or direct article-by-ID fetching are workarounds rather than dead ends.

Resources