Skip to main content
Glama
Open Market Research MCP

Open Market Research MCP

by mgifford

list_research_sources

Lists curated source descriptors for government acquisition research, with optional category filtering. Use it to discover available sources before planning market research; it does not query live government APIs.

Instructions

List curated source descriptors. This does NOT query live government APIs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_research_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: results come from a curated static corpus rather than live government APIs, implying no network calls and fixed freshness. It says nothing about pagination, result size, or filtering behavior beyond that single fact.

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?

Two short sentences with the core action front-loaded and zero filler, though the second sentence, while useful, is a negation that partly duplicates the scoping already implied by 'curated'.

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

Completeness3/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 no explanation, and the tool is simple with one optional parameter. The remaining gap is the undocumented category filter, which an agent needs in order to call it correctly.

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 'category' parameter has 0% schema description coverage and a default of empty string, neither of which the description explains. It does not say what valid categories exist, what an empty value does (presumably list all), or whether matching is exact or partial.

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?

The verb 'List' and resource 'curated source descriptors' are present, but 'descriptors' is jargon that leaves the actual content ambiguous, and nothing distinguishes this from the sibling find_research_sources. An agent gets a rough idea but must open the schema to know what is being listed.

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?

The only guidance is a negative: 'This does NOT query live government APIs.' There is no statement of when to call this versus find_research_sources or any other sibling, no prerequisites, and no conditions under which it should be avoided.

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