Skip to main content
Glama

Abn Lookup

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

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

Despite strong annotations (readOnly, idempotent, openWorld, non-destructive), the description adds meaningful behavior: data sources (SEC EDGAR/XBRL, FAERS, FDA), exact metrics pulled, correct handling of off-calendar fiscal years, sorting by primary metric, and pipeworx:// citation URIs. No statement conflicts with the 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 dense but front-loaded with triggers and the key preference rule before source details. The 'Replaces 8–15 sequential lookups' phrase is mildly promotional but not redundant; overall it earns its length.

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?

With no output schema, the description covers return expectations (paired data, sorting, citation URIs), the two entity types, input constraints, and important domain caveats. An agent has enough context to select and invoke the tool correctly without needing additional metadata.

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 already 100%, but the description enriches both parameters: type='company' maps to LATEST 10-K financial metrics and type='drug' maps to adverse-event/approval/trial counts. It also clarifies values as tickers/CIKs vs drug names, going well beyond the schema's short descriptions.

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 names a specific verb-resource pairing ('side-by-side comparison of 2–5 companies or drugs') and lists natural-language triggers ('X vs Y', 'which is bigger', 'rank these companies'), making the tool's purpose unmistakable. It also differentiates from sequential lookups, so it is not confused with entity_profile.

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?

It explicitly states when to use the tool via user-phrase examples and says to 'ALWAYS PREFER' it over 'sequential single-pack lookups' for comparison tasks. This provides a clear selection rule relative to the closest alternative, even though the sibling tool name isn't spelled out.

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

All Abn Lookup 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

Several tools have unclear or overlapping boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, while ask_pipeworx, deep_research, and validate_claim all handle factual lookup/research tasks. The five polymarket_* tools plus bet_research also overlap enough that an agent could easily pick the wrong entry point despite verbose descriptions.

Naming Consistency3/5

All names are snake_case and generally descriptive, but conventions are mixed: some are verb-first (ask_pipeworx, resolve_entity, validate_claim), some are noun-first (abn_lookup, entity_profile, polymarket_edges), and prefixes like pipeworx_ and polymarket_ are used inconsistently. It is readable but not a clean, predictable pattern.

Tool Count2/5

34 tools is far too many for a server named 'Abn Lookup' — most of the surface is a broad data-research platform with prediction-market analysis, memory, subscriptions, feedback, and web utilities. The count could fit a large platform, but under this server name and with several near-duplicate entry points, it feels bloated.

Completeness4/5

For a read-only lookup/research server, coverage is strong: ABR lookups, entity resolution, single-query research, grounded verification, deep research, company profiles, comparisons, change feeds, prediction-market analysis, memory, and subscriptions are all represented. Minor gaps exist (e.g., no ACN search-by-name, no order execution), but no core workflow dead-ends.

Resources