Skip to main content
Glama
Open Market Research MCP

Open Market Research MCP

by mgifford

find_research_sources

Locate relevant source directories, guidance, and upstream MCP servers to support government acquisition market research.

Instructions

Find relevant source directories, guidance, and upstream MCP servers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_research_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and it discloses almost nothing: it does not say whether the lookup is read-only, how results are ranked or scored, whether results are truncated, or what permissions are needed. "Upstream MCP servers" hints at a networked component without explaining any consequence of that.

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?

It is a single compact sentence with the action front-loaded and no filler. The brevity is not the problem; the missing content is a specification gap rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but for a single-argument discovery tool the description should still define what the query matches and how it differs from list_research_sources. Neither is present, and with no annotations there is no compensating structured data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter "query" has 0% schema description coverage, so the description is the only place semantics could come from, and it says nothing about accepted format (keywords vs. natural-language question), matching behavior, or expected length. That leaves the one required argument undefined in both schema and prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Find relevant source directories, guidance, and upstream MCP servers" gives a verb and a rough resource list, but the three categories are disparate (directories, guidance docs, MCP servers) and no scope or criterion for "relevant" is given. An agent knows it searches something, but not precisely what kind of object is returned versus what list_research_sources returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of the obvious sibling list_research_sources, which reads as the enumeration counterpart to this search tool. The agent must infer that this is the discovery tool and list_ is the enumeration tool without any statement to that effect.

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