Skip to main content
Glama

Abn Lookup

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

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

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description goes beyond annotations by disclosing the return format: top-N relevant tools with names, descriptions, and full input schemas, ready to call directly without a second lookup. This is useful behavioral context. It doesn't contradict the readOnlyHint, idempotentHint, or destructiveHint 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 the core purpose, then provides return details and usage guidance. The domain list is long but serves to clarify the scope. Each sentence earns its place, though the list could be slightly trimmed without losing meaning.

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?

For a tool-discovery tool with no output schema, the description sufficiently explains both invocation and expected results. It names the input type, the output fields, and the ready-to-call nature of results, making the tool fully usable with the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description reinforces that the query is a natural-language task description and mentions top-N results, but it doesn't add meaning beyond what the schema already documents for each parameter.

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's purpose: finding tools by describing the data or task, and explicitly lists the covered domains. It distinguishes itself from sibling tools by being the meta-search layer, not a domain-specific data lookup tool.

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?

The description explicitly tells the agent when to use this tool: when browsing, searching, looking up, or discovering tools, and instructs to call it FIRST when many tools are available. This provides clear routing guidance even though it doesn't name a specific alternative, since no sibling serves the same discovery role.

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