Skip to main content
Glama
Sign In
awwwards-mcp

awwwards-mcp

by INSANE0777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_stack

Read-onlyIdempotent

Fingerprint any URL's framework, CSS framework, and marker libraries from fetched HTML in one polite request—no browser required.

Instructions

Fingerprint a page's framework (Next.js/Astro/Nuxt/Remix/SvelteKit/WordPress/Webflow/Framer), CSS framework (Tailwind/Bootstrap), and marker libs from fetched HTML — runs on any URL, one polite request, no browser

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": {
      "url": "<url>"
    },
    "name": "analyze_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to fetch and fingerprint
timeoutMsNoFetch timeout in ms (default 15000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.13.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Addedv1.11.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real behavior: exactly one HTTP request per call and no browser, which tells the agent it is lightweight and will miss client-side-injected frameworks. It omits failure semantics (non-HTML responses, unreachable hosts).

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?

A single compact sentence that front-loads the fingerprint targets and ends with the execution constraints. Dense but zero filler; only mild cost is that the enumerations crowd out the when-to-use signal.

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, the description helpfully enumerates the detection vocabulary (Next.js/Astro/Nuxt/Remix/SvelteKit/WordPress/Webflow/Framer, Tailwind/Bootstrap), which sets return-value expectations. Missing is what happens when nothing is detected or the fetch fails.

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% (url and timeoutMs with default and 1–30s bounds documented inline), so the schema carries the parameter burden. The description adds nothing about parameters, which is acceptable at this coverage level.

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?

Specific verb 'Fingerprint' with an enumerated resource set (framework, CSS framework, marker libs) and an input source (fetched HTML). An agent knows exactly what comes out, though it never names a sibling (e.g. analyze_page_structure or analyze_bundle) to contrast against.

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 'runs on any URL, one polite request, no browser' — i.e. cheap static check, no JS rendering — but there is no explicit 'use this when X, use capture_live_site/analyze_bundle when Y' routing. The agent must infer the tradeoff against browser-based siblings.

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