Skip to main content
Glama

hallmark_sloplint

Audits HTML, JSX, TSX, Svelte, and Vue files for generic AI design tells, calculates a slop score, and fails the scan above a configurable threshold.

Instructions

Anti-AI-slop design auditor. Scans HTML, JSX, TSX, Svelte, and Vue files for generic AI tells (purple gradients, predictable 3-card grids, unanchored blur orbs, corporate buzzwords).

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": "hallmark_sloplint"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoPath to file or directory to scan.
fail_underNoSlop score failure threshold (default: 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description must carry behavioral disclosure; 'auditor' and 'Scans' do imply a read-only inspection, but that is never stated. It also does not disclose whether anything is written, what a slop score is, or how the fail_under threshold affects the run, which is a notable gap for a tool with no annotation coverage.

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 sentences, front-loaded with the tool's identity followed by concrete detection examples. Every clause earns its place and there is no filler.

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 scanner this covers what is scanned and what is looked for, but with no output schema the description never explains what the scan returns (violations list, per-file scores) or what the 'slop score' threshold is compared against. That leaves a real gap for an agent trying to interpret results.

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 both 'target' (path to file or directory) and 'fail_under' (slop score threshold, default 25) are already documented in the schema. The description adds no syntax, format, or behavioral meaning beyond that, so the baseline of 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?

Names a specific verb ('Scans') and resource ('HTML, JSX, TSX, Svelte, and Vue files'), then enumerates the exact patterns it detects (purple gradients, 3-card grids, blur orbs, buzzwords). This is concrete enough that an agent can tell it apart from a general frontend checker 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?

Usage is implied by 'auditor' and the listed file types, so an agent can infer it should be used when reviewing design/AI-generated UI code. However, there is no explicit when-to-use or when-not-to-use statement, no mention of what fail_under is for (e.g., CI gating), and no guidance relative to alternatives.

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