Skip to main content
Glama

Extract a website's design tokens as JSON

design_tokens
Read-only

Extract a website's design tokens as JSON: color palette with roles (hex), fonts and type scale, spacing, border radii, shadows, light/dark mode, and a ready-to-use Tailwind theme extension. Takes 5-20 s. Price: $0.02 per call (x402, USDC on Base). Without payment, returns the payment requirements.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only and open-world annotations, it discloses a 5–20 second runtime, a concrete $0.02 per-call price, the payment network and currency, and the unpaid call's payment-requirements response. These details give the agent useful operational and cost expectations before invocation.

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?

The purpose and output are front-loaded, followed by compact latency, price, and unpaid-call details. Despite the long output list, each item helps define the result and there is no filler.

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

Completeness5/5

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

For a two-parameter extraction tool, the combined definition covers the expected output, runtime, cost, payment behavior, and invocation requirements. Although there is no output schema, the enumerated JSON contents and Tailwind extension provide enough return-value context for correct selection and use.

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?

Both parameters already have complete schema descriptions, including the public URL constraint and the base64 payment-signature workflow. The description adds the concrete price, but otherwise largely repeats the schema's payment guidance rather than supplying substantial new parameter semantics.

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 uses a specific verb and resource—extracting a website's design tokens as JSON—and concretely identifies the colors, typography, spacing, radii, shadows, modes, and Tailwind output. This makes the result easy to understand, but it does not explicitly differentiate the tool from siblings such as brand_kit or clone_ui.

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?

The detailed output inventory and ready-to-use Tailwind theme extension provide clear context for when the tool is useful, while the final sentence explains how to begin without payment. It does not provide exclusions or explicit guidance for choosing an alternative tool.

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.