Govcon 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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety profile is covered. The description adds valuable behavioral context beyond annotations: it returns top-N tools with full input schemas, includes curated examples, and makes results directly callable without a second lookup. This helps the agent know exactly what to expect from the response.

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 three sentences, front-loaded with the core purpose, then usage context, then return-value details. The list of topic areas is somewhat long but directly helps the agent judge relevance, and no sentence is wasted.

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?

There is no output schema, so the description carries the full burden of explaining return values. It clearly states that results include names, descriptions, and full input schemas with curated examples, and that results are ready to call directly. This fully covers the agent's need to understand what the tool returns and how to use it.

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%, so all six properties including aliases are documented in the input schema. The description reinforces that the query should be a natural language description of the desired task but adds no semantics beyond the schema; thus the 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 opens with 'Find tools by describing the data or task' — a specific verb and resource that clearly differentiates this meta-search tool from the domain-specific sibling tools. It explicitly lists the use cases (browse, search, look up, discover) and the breadth of topic areas, making the purpose unmistakable.

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 says 'Use when you need to browse, search, look up, or discover what tools exist' and 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This gives strong positive guidance and implies a contrast with directly calling a known tool, though it does not explicitly name alternatives or exclusion criteria.

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

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

Disambiguation3/5

Several tools have overlapping purposes (e.g., ai_visibility_check and scan_competitor_ai_presence; ask_pipeworx, ask_pipeworx_grounded, and deep_research). However, detailed descriptions and specific use cases help agents distinguish between them in most cases.

Naming Consistency5/5

All tools use snake_case naming consistently, e.g., ask_pipeworx, compare_entities, govcon_agency_landscape. The pattern is uniform across the entire set.

Tool Count4/5

With 33 tools, the set is slightly over the typical well-scoped range. While many tools serve distinct purposes, some seem redundant (e.g., memory tools, multiple research tools), making the count feel a bit heavy.

Completeness3/5

The tool surface covers a broad range of research and intelligence domains but lacks actionable tools for core government contracting tasks like submitting bids or tracking contract performance. Several obvious operations (e.g., user profile management, submission tools) are missing.

Resources

Need Help?