Skip to main content
Glama
Open Market Research MCP

Open Market Research MCP

by mgifford

create_research_plan

Generates a DITAP-compatible human-centered market research sequence to structure compliant government acquisition research planning.

Instructions

Give a DITAP-compatible human-centered market research sequence.

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": "create_research_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, yet it says nothing about side effects, whether a plan is persisted or merely generated, whether it depends on previously located sources, or what the caller receives. One sentence about output type is not enough for a tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler, which is structurally clean. It is arguably too sparse rather than bloated, so conciseness itself is not the problem.

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 spelled out, but the description still leaves the core concept opaque: an agent cannot judge what a DITAP-compatible sequence is or whether it needs prior research inputs. For a planning/orchestration tool that presumably anchors a workflow, this is under-described.

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

Parameters4/5

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

The schema defines zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The one missed opportunity is that the description does not explain what the tool uses as implicit context given the absence of inputs.

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 description gives a verb-resource pair ("Give ... market research sequence"), so an agent can tell this produces a research plan rather than a report, source list, or gap analysis. But it leans on unexplained jargon ("DITAP-compatible", "human-centered") and never states what the returned sequence actually contains or how it differs concretely from the sibling planning/report tools. The purpose is inferable but imprecise.

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 statement of when to call this versus siblings like draft_market_research_report or identify_accessibility_evidence_gaps, no prerequisites, and no indication of what inputs or prior context the tool expects. The single sentence offers no usage context at all.

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