Pharma Intel

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

Name	Required	Description
`q`	No	Alias for query.
`task`	No	Alias for query.
`limit`	No	Maximum number of tools to return (default 20, max 50)
`query`	Yes	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.
`search`	No	Alias for query.
`description`	No	Alias for query.

Schema Changelog

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

Changed5 schema fields changedJun 3, 2026

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"
+}

Changed1 schema field changedMay 26, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]

First observedApr 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already indicate safe, idempotent read-only behavior. The description adds significant behavioral context: it explains the return format ('top-N most relevant tools with names, descriptions, and full input schemas') and emphasizes that results are 'ready to call directly, no second schema lookup needed.' No contradiction with 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 a single paragraph of moderate length. It front-loads the purpose and provides useful details without unnecessary verbosity. Some structure (e.g., bullet points for the list of domains) could improve scannability, but it remains concise and informative.

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?

Given the tool's complexity (multiple aliases, no output schema), the description adequately covers behavior and output format. It explains that the tool returns 'full input schemas (with curated examples),' which is sufficient for an agent to use the results. No critical 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 description coverage is 100%; all parameters are documented with aliases. The description adds minimal extra meaning beyond the schema; it mentions 'query' implicitly but does not describe the aliases or the limit parameter in detail. Baseline score of 3 is appropriate.

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 specifies the verb ('discover'), the resource ('tools'), and the context ('by describing the data or task'). The list of example domains further clarifies its scope, distinguishing it from sibling tools that perform specific analyses or retrievals.

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?

The description explicitly recommends using this tool first: 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This provides clear guidance on when to use it. While it does not explicitly state when not to use it, the context implies it is for exploration, not direct answers.

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

All Pharma Intel tools Inspect

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

A4.1/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose, even within the same domain (e.g., ask_pipeworx vs ask_pipeworx_grounded vs ask_pipeworx_beta are differentiated by groundedness/beta status; polymarket_edges vs polymarket_arbitrage vs polymarket_fill_risk each target discovery vs arbitrage vs execution risk). The descriptions are highly detailed, eliminating ambiguity about when to use each.

Naming Consistency4/5

All tool names use snake_case consistently, and most follow a verb-first pattern (ask_, compare_, discover_, search_, validate_), but a few are noun-first (entity_profile, polymarket_edges, recent_alerts). The style is readable and predictable, though not perfectly uniform in the verb_noun convention.

Tool Count2/5

With 37 tools, the server is heavily over-scoped, especially given the 'Pharma Intel' name that suggests a focused pharma domain. Many tools are general-purpose (prediction markets, memory, subscription management, feedback) unrelated to the server's apparent purpose, making it feel like a grab bag rather than a cohesive set.

Completeness4/5

The pharma-specific tools cover drug profiles, safety, pipeline scans, catalysts, indication landscapes, and sponsor diligence – a solid lifecycle coverage. The broader data/query/prediction-market tools also feel complete for their respective sub-domains. The only minor gaps are niche operations (e.g., updating a subscription), but these are not critical to the core workflows.

Resources

Need Help?