Skip to main content
Glama

frontend_sentinel

Audits React, Vue, and HTML templates to find accessibility defects, mobile viewport breaks, and hydration hazards before release.

Instructions

Audits React, Vue, and HTML templates for accessibility defects, mobile viewport breaks, and hydration hazards.

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": {
      "path": "<path>"
    },
    "name": "frontend_sentinel"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to file or folder to audit
html_reportNoOptional output path for HTML report

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It names the defect classes checked, but does not state whether the audit is read-only, whether it writes the optional HTML report, what permissions are needed, or what the result contains.

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?

Single sentence, front-loaded with the verb and scope, with no redundant wording. Every phrase contributes to the audit scope.

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?

For a two-parameter audit tool with no annotations and no output schema, the description identifies the audit scope but omits return/report behavior and side effects. It is adequate at a high level but not fully complete.

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 coverage is 100%, so both path and html_report are already documented in the schema. The description adds no syntax, format, or constraint details beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Audits') and resources ('React, Vue, and HTML templates') plus the defect categories checked. An agent can identify the tool's function without opening the schema.

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 the tool is for auditing React, Vue, and HTML templates, but gives no explicit when-to-use or when-not-to-use guidance and names no alternatives. The implied context is clear enough for a 3.

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