Skip to main content
Glama
Open Market Research MCP

Open Market Research MCP

by mgifford

import_openacr_report

Imports OpenACR YAML so you can inspect accessibility report data; it never creates or certifies an ACR.

Instructions

Import OpenACR YAML for inspection. Never creates or certifies an ACR.

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": {
      "openacr_yaml": "<openacr_yaml>"
    },
    "name": "import_openacr_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
catalog_yamlNo
openacr_yamlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/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 behavioral burden. It does valuable work by declaring the tool is non-mutating with respect to ACR creation/certification, which is the highest-risk ambiguity for an import tool. However, it does not say whether the imported document is persisted, whether validation errors are surfaced, or what the parse result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the positive scope front-loaded and the strongest safety constraint immediately after. There is no filler and every clause carries information.

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?

There is no output schema, so the description should say what an inspection yields (parsed structure, validation results, summary), and it does not. Combined with the unmentioned catalog_yaml parameter, the definition is adequate for a simple parse tool but leaves real gaps an agent would hit on first invocation.

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?

Schema description coverage is 0%, so the description must compensate and it largely does not. "openacr_yaml" is only indirectly gestured at by the phrase "OpenACR YAML", and the optional "catalog_yaml" parameter is not mentioned at all — an agent has no basis to decide whether to supply it. This is a significant gap for a 2-parameter tool with zero schema documentation.

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?

"Import OpenACR YAML for inspection" gives a specific verb (import) and a specific resource format, and the second sentence clarifies the negative scope (never creates or certifies). An agent can tell this is a parse/read operation rather than a report-creation step. It stops short of a 5 because it never names or contrasts with the sibling workflow tools it coexists with.

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?

"For inspection" implies the use case and "Never creates or certifies an ACR" rules out one misuse, which is genuinely useful negative guidance. But there is no explicit statement of when an agent should call this versus the sibling planning/evidence tools, and no prerequisites (e.g., that the YAML must be a valid OpenACR document).

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