ai-verify-mcp

Overview Schema Related Servers Score Discussions

validation_matrix

Run multi-dimensional validation (functional, visual, performance, accessibility) with role-based permission checks and generate a comprehensive score report.

Instructions

执行多维度验证矩阵（功能/视觉/性能/a11y），输出综合评分报告。支持角色×功能权限矩阵验证，每个角色使用独立 session。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`har`	No	是否导出 HAR JSON，默认 true
`url`	Yes	目标页面 URL
`name`	No	矩阵验证名称
`roles`	Yes	角色列表，每个角色可包含 name、sessionName、url、setupSteps
`features`	Yes	功能列表，每个功能可包含 name、steps、stepsByRole、expected、expectedByRole、assertions、assertionsByRole、focus
`dimensions`	No	验证维度列表，可选：functional、visual、performance、a11y
`instrument`	No	是否注入运行时探针，默认 true
`clearErrors`	No	执行前是否清空错误 checkpoint，默认 true
`a11yStandard`	No	a11y 标准级别：wcag-a / wcag-aa / wcag-aaa	wcag-aa
`outputFormat`	No	输出格式：json / markdown	json
`clearArtifacts`	No	执行前是否清理证据产物，默认 false
`visualBaseline`	No	视觉基线截图路径（可选）
`continueOnFailure`	No	单元失败后是否继续执行后续功能，默认 false
`investigateOnFailure`	No	失败时是否自动 debug_investigate，默认 true
`performanceThreshold`	No	性能阈值（LCP ms），默认 2500

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Addedv1.9.5Jul 22, 2026
Removedv1.9.1Jul 17, 2026

Changed1 schema field changedv1.8.5Jul 16, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "artifacts": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "dimensions": {
-      "properties": {
-        "a11y": {
-          "description": "无障碍维度评分",
-          "type": "object"
-        },
-        "functional": {
-          "description": "功能维度评分",
-          "type": "object"
-        },
-        "performance": {
-          "description": "性能维度评分",
-          "type": "object"
-        },
-        "visual": {
-          "description": "视觉维度评分",
-          "type": "object"
-        }
-      },
-      "type": "object"
-    },
-    "grade": {
-      "description": "等级 A/B/C/D/F",
-      "type": "string"
-    },
-    "name": {
-      "type": "string"
-    },
-    "overallScore": {
-      "description": "综合评分 0-100",
-      "type": "number"
-    },
-    "recommendations": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "roleMatrix": {
-      "description": "角色×功能矩阵结果",
-      "type": "array"
-    },
-    "success": {
-      "type": "boolean"
-    },
-    "timestamp": {
-      "type": "string"
-    },
-    "url": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed8 schema fields changedv1.2.1Jul 7, 2026

addedInput schema / properties / a11yStandard

Added value: +{
+  "default": "wcag-aa",
+  "description": "a11y 标准级别：wcag-a / wcag-aa / wcag-aaa",
+  "type": "string"
+}

addedInput schema / properties / dimensions

Added value: +{
+  "default": [
+    "functional",
+    "visual",
+    "performance",
+    "a11y"
+  ],
+  "description": "验证维度列表，可选：functional、visual、performance、a11y",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / outputFormat

Added value: +{
+  "default": "json",
+  "description": "输出格式：json / markdown",
+  "type": "string"
+}

addedInput schema / properties / performanceThreshold

Added value: +{
+  "description": "性能阈值（LCP ms），默认 2500",
+  "type": "number"
+}

addedInput schema / properties / url

Added value: +{
+  "description": "目标页面 URL",
+  "type": "string"
+}

addedInput schema / properties / visualBaseline

Added value: +{
+  "description": "视觉基线截图路径（可选）",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "roles",
-  "features"
-]New value: +[
+  "url",
+  "roles",
+  "features"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "artifacts": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "dimensions": {
+      "properties": {
+        "a11y": {
+          "description": "无障碍维度评分",
+          "type": "object"
+        },
+        "functional": {
+          "description": "功能维度评分",
+          "type": "object"
+        },
+        "performance": {
+          "description": "性能维度评分",
+          "type": "object"
+        },
+        "visual": {
+          "description": "视觉维度评分",
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "grade": {
+      "description": "等级 A/B/C/D/F",
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "overallScore": {
+      "description": "综合评分 0-100",
+      "type": "number"
+    },
+    "recommendations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "roleMatrix": {
+      "description": "角色×功能矩阵结果",
+      "type": "array"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "timestamp": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv1.2.0Jun 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions independent sessions per role but does not disclose side effects, auth requirements, rate limits, or whether the tool is read-only or mutates state. The behavioral impact is underdescribed.

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?

The description is two concise sentences that front-load the core purpose and key details. Every word contributes meaning, and there is no redundancy.

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?

With 15 parameters and no output schema or annotations, the description is too brief. It does not explain the output report format, prerequisites, or how to interpret results, leaving significant gaps for a complex tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema documents all parameters. The description adds no additional semantic value beyond what the schema provides, meeting the baseline.

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

Purpose5/5

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

The description explicitly states the tool's function: executing a multi-dimensional validation matrix covering functional, visual, performance, and a11y dimensions, and outputting a comprehensive scoring report. It also mentions role×feature permission matrix validation with independent sessions, which clearly differentiates it from sibling tools like browser_matrix_test or validation_run.

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 description implies usage for comprehensive multi-dimensional and role-based validation but does not explicitly state when to use this tool over alternatives or provide context on when not to use it. No comparisons or exclusions are given.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/validpilot/ai-verify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server