Skip to main content
Glama
Sign In
handmade

handmade

by h-hiram
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

handmade_scan

Scan UI source files for patterns that make an interface look AI-generated. Returns a 0-100 score plus each finding with file, line and a concrete fix.

Instructions

Scan UI source code (HTML, CSS/SCSS, Tailwind, JSX/TSX, Vue, Svelte, Astro, Laravel Blade, Angular) for patterns that make an interface look AI-generated. Returns a 0-100 score and each finding with file, line and a concrete fix. Run it after building or changing UI and fix what it reports. Use an absolute path.

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

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to a folder or file.
formatNotext
ignoreNoComma-separated tell IDs or categories to skip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a fair job: it discloses that the tool reports rather than mutates, describes the return shape (score, per-finding file, line, concrete fix), and prescribes a follow-up action. It omits whether the scan is strictly read-only, how large a codebase it handles, and what a "tell ID" or category is.

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?

Three sentences, front-loaded with scope, then returns, then the workflow instruction and a usage constraint. No sentence is filler and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description compensates well by describing return values and the post-scan workflow. It stops short of explaining the ignore vocabulary or confirming read-only behavior, which matters for a tool pointed at a whole source tree.

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 67% and the description reinforces only the path parameter ("Use an absolute path"). The format enum and the ignore parameter's tell-ID/category vocabulary are left entirely to the schema, with no explanation of where tell IDs come from.

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 UI source code") and enumerates the supported syntaxes (HTML, CSS/SCSS, Tailwind, JSX/TSX, Vue, Svelte, Astro, Blade, Angular), so an agent knows exactly what input it accepts. It also states the output (0-100 score plus findings). It does not differentiate itself from the sibling handmade_check or handmade_fix_plan, which overlap conceptually.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Run it after building or changing UI and fix what it reports" gives a clear triggering condition. There is no explicit when-not guidance or routing to alternatives such as handmade_list_tells for discovering tell IDs, so the agent must infer that relationship.

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

Deploy Server

Other Tools