Skip to main content
Glama
ReftrixMCP
by TKMD

quality.evaluate

Read-onlyIdempotent

Evaluate web design quality across originality, craftsmanship, and contextuality, with AI cliché detection and actionable recommendations to identify generic patterns and improve pages.

Instructions

Evaluate web design quality on 3 axes (originality, craftsmanship, contextuality) with AI cliche detection

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": "quality.evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNoHTML content (direct, max 10MB)
pageIdNoWebPage ID (UUID, from DB)
strictNoStrict mode: stricter AI cliche detection (default: false)
contextNoEvaluation context (v0.1.0)
summaryNoLightweight mode: exclude detailed info and return summary only (v0.1.0 MCP-RESP-01, v0.1.0 default true). When true (default): recommendations max 3, contextualRecommendations max 3, patternAnalysis arrays max 3, axeAccessibility.violations max 5, clicheDetection.patterns max 3. Set to false for full details.
weightsNoAxis weights (sum 1.0)
targetAudienceNoTarget audience (e.g. enterprise, consumer, professionals)
targetIndustryNoTarget industry (e.g. healthcare, finance, technology)
use_playwrightNoUse Playwright for runtime aXe accessibility testing (default: false, uses JSDOM)
patternComparisonNoPattern comparison options for pattern-driven evaluation (v0.1.0)
responsive_evaluationNoResponsive quality evaluation using Playwright (v0.1.0). Measures touch targets, readability, overflow, and responsive images across viewports.
includeRecommendationsNoInclude recommendations (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / responsive_evaluation / properties / viewports / maxItems
      Added value: +10
  2. Addedv0.1.8

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety is covered. The description adds only that cliche detection exists and that three axes are scored, but does not disclose the cost/behavioral implications of heavy options such as use_playwright runtime testing, responsive_evaluation network fetches, or the summary vs full-detail mode, which materially change what the agent receives.

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?

A single tightly written sentence with the core capability front-loaded and zero filler. Nothing is redundant, though the brevity is also the source of the definition's gaps elsewhere.

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 12-parameter tool with nested objects, browser-based responsive evaluation, Playwright aXe testing, and no output schema, one sentence is far too thin. The agent gets no sense of the report shape (scores, recommendations, cliche patterns, accessibility violations) or the trade-offs between lightweight summary mode and full detail.

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 all 12 parameters including nested weights, context, and responsive_evaluation are already documented in the schema. The description's mention of the three axes lightly frames the weights object but adds no syntax or interaction detail beyond that, so the baseline 3 applies.

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?

The description names a specific verb (evaluate) and resource (web design quality), and enumerates the three scoring axes plus AI cliche detection. This distinguishes it reasonably from siblings like performance.evaluate and accessibility.audit, though it never explicitly contrasts itself with design.compare or design.regression_test.

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 guidance on when to invoke this tool, when to use an alternative, or what prerequisites exist. Notably, the tool accepts either raw HTML or a pageId and the description says nothing about which to supply or what happens if neither is given, leaving the agent to infer invocation conditions from the schema alone.

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