Open Market Research MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_research_sourcesC | List curated source descriptors. This does NOT query live government APIs. |
| find_research_sourcesC | Find relevant source directories, guidance, and upstream MCP servers. |
| create_research_planC | Give a DITAP-compatible human-centered market research sequence. |
| identify_accessibility_evidence_gapsB | List verification questions for one candidate, without deciding conformance. |
| draft_market_research_reportB | Render a local research record into an unapproved Markdown draft. |
| import_openacr_reportB | Import OpenACR YAML for inspection. Never creates or certifies an ACR. |
| normalize_public_metadataB | Normalize local code.json, agency-index.json, or publiccode.yml text. This performs no network request and does not treat metadata as proof of suitability, reuse rights, or accessibility conformance. |
| map_1102tools_usaspending_recordB | Map one selected public USAspending record into a reviewable evidence draft. This makes no network request and does not apply the record to a research file. The host must obtain explicit human approval before applying it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| curated_sources | Read the source directory and its limitations. |
| workflow | Read the deterministic market research workflow. |
TDQS
Scored across 8 tools
Most tools occupy clearly distinct stages of a market-research workflow (plan, source discovery, gap analysis, drafting, metadata import/mapping). The only genuinely adjacent pair is list_research_sources vs find_research_sources, whose boundary (curated descriptors vs directories/guidance/upstream servers) is stated but still easy to confuse. The remaining six tools are unambiguous.
Every tool follows a snake_case verb_noun pattern (list_, find_, create_, identify_, draft_, normalize_, import_, map_), with no camelCase or bare-noun outliers. The one long name, map_1102tools_usaspending_record, embeds product nouns but still conforms to the same verb-first convention.
Eight tools is a good scope for a niche research pipeline, with each mapping to a discrete step rather than duplicating work. A couple of tools (import_openacr_report, normalize_public_metadata) are narrow single-format utilities, which slightly inflates the surface relative to the broader planning tools.
The set covers discovery, planning, gap analysis, and output rendering, but there is no tool to persist a research record, candidate, or evidence artifact—several tools explicitly defer application to the host, leaving dead ends for an agent working end-to-end. There is also no update/edit or retrieval-by-id operation for existing records, only rendering of 'a local research record' assumed to already exist.