Skip to main content
Glama

Complex Portal

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

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint, which the description complements by explaining the return format: '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.' This adds behavioral detail beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Description is compact yet comprehensive: states purpose, usage, return characteristics, and a direct instruction ('Call this FIRST...'). No redundant sentences; all earn their place.

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 the tool's complexity (discovery with aliases, no output schema), the description fully covers what it does, when to use it, and what the output contains. No gaps remain.

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% with 6 parameters all described. The description mentions query and limit but doesn't add significant meaning beyond schema aliases and examples already present. Baseline score of 3 is appropriate as the description adds minimal extra semantic value.

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 'Find tools by describing the data or task' with a specific verb (find), resource (tools), and method (natural language query). It distinguishes from sibling tools like search_complexes or ask_pipeworx by focusing on discovery of available tools.

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?

Explicit guidance: 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' Lists concrete use cases (browse, search, look up) and domains (SEC filings, FDA drugs, etc.), implicitly telling when not to use it (when you need a single answer from a specific 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

Several tools serve nearly identical purposes: ask_pipeworx and ask_pipeworx_beta are currently functionally identical, and polymarket_edges, polymarket_arbitrage, and bet_research all hunt prediction-market opportunities with overlapping outputs. The verbose descriptions help, but an agent can easily call the wrong one.

Naming Consistency4/5

All 33 names use lowercase snake_case with descriptive, mostly verb-first words (ask_, compare_, discover_, search_), and domain suites are consistently prefixed (polymarket_*, pipeworx_*). Minor deviations like entity_profile or recent_changes (noun/adjective-first) keep it from a perfect 5.

Tool Count2/5

33 tools is well into the 'too many' range, especially for a server nominally about the narrow Complex Portal database. Many tools (memory, feedback, subscriptions, trending) are generic meta-utilities unrelated to the stated purpose.

Completeness2/5

For the stated 'Complex Portal' domain, only search_complexes and get_complex exist, with no organism-scoped search, batch access, or additional lifecycle coverage, making the surface severely incomplete for that name. The actual Pipeworx platform is broadly covered, but the server-name mismatch makes the set feel incomplete for its advertised purpose.

Resources