Skip to main content
Glama

Lazynext AI Slop Checker

scan_html

Scan HTML markup for AI-slop writing AND visual design tells (gradients, kickers, glassmorphism, stat rows, ...).

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": {
      "html": "<html>"
    },
    "name": "scan_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesHTML document to scan
profileNoseverity profile (default | strict | lenient)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It helpfully discloses the scope of detection (both prose tells and visual design patterns), but says nothing about read-only nature (implied by 'scan'), whether it analyzes a fragment or full document, or what the findings output looks like despite there being no output schema.

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

Conciseness4/5

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

One tightly written sentence with the verb and resource front-loaded and examples used efficiently to convey scope. The trailing ellipsis leaves the tell list open-ended, which is acceptable but slightly less crisp than an enumerated scope statement.

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 scanning tool with no annotations and no output schema, the definition covers what is scanned but not what comes back (findings, severities, counts) or how profile changes results. That is a meaningful gap for an agent deciding whether this call answers its question.

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 parameters are already documented in the schema. The description adds nothing about the profile parameter's effect on results or the expected size/shape of the html input, 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?

Names a specific verb and resource ('Scan HTML markup') and goes further by stating the two detection domains: AI-slop writing and visual design tells, with concrete examples (gradients, kickers, glassmorphism, stat rows). This lets an agent distinguish it from scan_text or scan_render by the artifact type it accepts, though it never names those siblings explicitly.

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 when-to-use guidance, no contrast with scan_text or scan_project, and no explanation of when strict or lenient profiles are appropriate. Usage is only inferable from the fact that the tool takes HTML.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.