Skip to main content
Glama

Intercom

by io.github.pipeworx-io

Ask Pipeworx

ask_pipeworx
Read-onlyIdempotent

PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 5,798 tools across 1517 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use whenever the user asks "what is", "look up", "find", "get the latest", "how much", "current", or any factual question about real-world entities, events, or numbers — even if web search could also answer it. Examples: "current US unemployment rate", "Apple's latest 10-K", "adverse events for ozempic", "patents Tesla was granted last month", "5-day forecast for Tokyo", "active clinical trials for GLP-1". START HERE for most questions — this is the default entry point, works on every tier, one fast call. Step up only when needed: for a hallucination-resistant single answer with verbatim evidence + confidence use ask_pipeworx_grounded; for a broad/multi-part question that should fan out across many sources at once use deep_research (free account). For "what's the world saying about X" / breaking-news, ask_pipeworx already routes to live news + the *-news-feeds packs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
queryNoAlias for question.
promptNoAlias for question.
questionYesYour question or request in natural language. Accepts query, q, prompt, text, input as aliases.

Schema Changelog

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

  1. Changed6 schema fields changed
    • addedInput schema / properties / input
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • addedInput schema / properties / prompt
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • changedInput schema / properties / question / description
      Previous value: -"Your question or request in natural language"New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "question": "What was Apple's revenue in 2024?"
+  },
+  {
+    "question": "Any recent SEC filings for $NVDA?"
+  },
+  {
+    "question": "Current price of bitcoin"
+  }
+]
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses routing behavior, argument filling, stable pipeworx:// citation URIs, and caching/lag caveats for real-time sports, stocks, crypto, and forex data. It also states limitations such as not being for opinions and not covering inaccessible paywalled/old/unlisted data well.

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 long, but most sentences earn their place because this routing tool has many siblings and needs exclusion guidance. It front-loads the core instruction and organizes alternatives in a readable sequence; the trailing incomplete sentence ('For a free account') and minor repetition prevent a perfect score.

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?

For a high-complexity router with no output schema, the description covers return behavior, domain coverage, trigger phrases, examples, and routes around most sibling tools. It is highly usable, though it does not specify failure modes, rate limits, or resource consumption, and the clipped final sentence leaves one use-case incomplete.

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%, so the baseline is 3. The description adds value by giving natural-language trigger phrases and concrete example questions that clarify what should go in the 'question' parameter. It does not specify length limits or multi-part question handling, but the examples are strong enough to guide correct usage.

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 role: it routes factual questions to one of 5,798 tools across 1,517 verified sources and returns structured answers with stable pipeworx:// citation URIs. It also explicitly differentiates itself from web search and several sibling tools, so the agent knows exactly what this tool is for.

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 provides explicit preference rules ('PREFER OVER WEB SEARCH', 'START HERE for most questions'), trigger phrases, example queries, and an extensive when-not-to-use list covering memory tools, ic_*, deep_research, bet_research, news feeds, web search, and ask_pipeworx_beta. There is no ambiguity about when this tool should be selected over alternatives.

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

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

B3.4/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route factual questions to the same underlying catalog with unclear boundaries. Polymarket tools also overlap (bet_research, polymarket_edges, polymarket_arbitrage), and ai_visibility_check vs scan_competitor_ai_presence are nearly the same operation.

Naming Consistency3/5

Most tools follow a readable snake_case verb_noun pattern (ask_pipeworx, entity_profile, resolve_entity, list_subscriptions). However, the set mixes two distinct naming families — ic_* for Intercom tools and pipeworx/* for the rest — and includes ambiguous generic names like remember/recall/forget that don't visually connect to the rest.

Tool Count2/5

36 tools is far more than needed for an Intercom-focused server; the vast majority have nothing to do with Intercom and instead cover a sprawling Pipeworx data-research, prediction-market, and memory/subscription toolkit. The count alone is in the 'too many' range, and the scope mismatch makes it feel even more inflated.

Completeness2/5

For a server named Intercom, the surface is severely incomplete: only read/list/search operations exist for contacts and conversations, with no create, update, delete, send-message, or company-detail operations. The unrelated Pipeworx tools are fairly broad, but they don't compensate for the missing Intercom lifecycle coverage that the server name promises.

Resources