Skip to main content
Glama
Open Market Research MCP

Open Market Research MCP

by mgifford

identify_accessibility_evidence_gaps

Lists verification questions for a single candidate to surface accessibility evidence gaps without deciding conformance. Use it to plan what evidence to request before review.

Instructions

List verification questions for one candidate, without deciding conformance.

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": {
      "candidate_json": "<candidate_json>"
    },
    "name": "identify_accessibility_evidence_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidate_jsonYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one important behavioral trait — that the tool will not render a conformance decision — but says nothing about read-only vs. mutating behavior, permissions, side effects, or whether the input candidate is modified. Return format is covered by the output schema, so that gap is excused.

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 short sentence with the action and the key boundary up front; nothing is padded or redundant. It is arguably too terse for the amount of undocumented structure it needs to convey.

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?

For a tool with no annotations, a required structured JSON parameter with no schema descriptions, and a research-oriented purpose, the description is under-specified. An agent cannot tell what a valid candidate_json looks like or what kind of questions ('verification questions' about what?) will come back, beyond what the output schema may reveal.

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?

There is one required parameter, candidate_json, with 0% schema description coverage. The description only says 'one candidate' and never indicates that the input is JSON, what shape that JSON must take, or which fields are needed for the tool to generate questions — leaving the sole parameter essentially undocumented.

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

Purpose4/5

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

States a specific verb and output ('list verification questions') and scopes it to 'one candidate', plus a negative boundary ('without deciding conformance') that separates it from a conformance-adjudication tool. The only weakness is that 'candidate' (candidate what?) is never defined, though the tool's domain makes it inferable.

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

Usage Guidelines3/5

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

The clause 'without deciding conformance' implies a workflow position: use this when evidence is incomplete and you need questions rather than a verdict. However, no positive trigger, prerequisites, or named alternative tool are given, so the agent must infer when to reach for this instead of a reporting or normalization sibling.

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