Skip to main content
Glama

Comtrade

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. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural 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."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds: returns top-N tools with full schemas and curated examples, ready to call directly, no second schema lookup needed. This adds useful behavioral context.

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 concise yet packed with information. Front-loaded purpose, then examples, then output details, then usage guidance. No redundant sentences.

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 with 6 params (1 required), high schema coverage, and no output schema, the description fully explains what it does and what it returns. The lack of output schema is compensated by describing the return structure.

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% (all 6 parameters described). Description adds value by explaining query as natural language, listing aliases, and providing example queries. This goes beyond the schema's basic 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 clearly states the tool's purpose: 'Find tools by describing the data or task.' It lists specific domains (SEC filings, financials, etc.) and return type (top-N tools with schemas). Distinguishes from siblings as a discovery tool.

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?

Explicitly states 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' Provides clear context for when to use, though does not mention when not to use.

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

All Comtrade 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
Disambiguation3/5

Some tools have near-identical purposes (ask_pipeworx vs ask_pipeworx_beta are currently identical; polymarket_arbitrage vs polymarket_edges both find opportunities), but detailed descriptions and distinct input patterns mostly help an agent choose. A few discovery/verification tools (suggest_questions vs discover_tools, validate_claim vs ask_pipeworx_grounded) also overlap, creating residual ambiguity.

Naming Consistency3/5

All names are snake_case and many use domain prefixes (comtrade_, polymarket_, pipeworx_), but the set mixes verb_noun (compare_entities, discover_tools), bare verbs (remember, forget, subscribe), and noun phrases (entity_profile, recent_changes). This inconsistency, plus the use of domain-specific prefixes as a substitute for a uniform verb_noun style, makes the naming pattern only moderately predictable.

Tool Count2/5

35 tools is well beyond the typical well-scoped range, and the vast majority (prediction markets, memory, subscriptions, feedback, npm dependency checks) have nothing to do with the server's apparent Comtrade trade-data purpose. This bloat makes the set feel unfocused, even though some meta-tools serve a general data-access mission.

Completeness4/5

For the Comtrade trade-data domain, the four comtrade_* tools cover country codes, top commodities, top partners, and detailed bilateral trade values — enough for most queries, with minor gaps like time-series trends or tariff lookups. For the broader Pipeworx data-access scope, the set is extensive (ask_pipeworx, deep_research, entity_profile, validate_claim, subscriptions), so no severe dead ends are apparent.

Resources