Skip to main content
Glama

Validate CSS

validate_css
Read-onlyIdempotent

Use this when raw CSS source is supplied. Parses it inside the Worker and returns syntax messages without contacting an external service.

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": {
      "css": "<css>"
    },
    "name": "validate_css"
  }
}

Input Schema

NameRequiredDescriptionDefault
cssYesRaw CSS source supplied by the user.

Output Schema

NameRequiredDescriptionDefault
errorNo
errorsYes
overviewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput 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 changed
    • changedOutput schema / properties / overview / properties / kind / enum
      Previous value: -[
      -  "html",
      -  "css",
      -  "seo",
      -  "schema",
      -  "links",
      -  "report"
      -]New value: +[
      +  "html",
      +  "css",
      +  "seo",
      +  "schema",
      +  "links",
      +  "report",
      +  "site"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / css / description
      Added value: +"Raw CSS source supplied by the user."
  4. Changed2 schema fields changed
    • addedOutput schema / properties / overview
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "counts": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "key": {
      +            "type": "string"
      +          },
      +          "label": {
      +            "type": "string"
      +          },
      +          "tone": {
      +            "enum": [
      +              "error",
      +              "warning",
      +              "info",
      +              "success"
      +            ],
      +            "type": "string"
      +          },
      +          "value": {
      +            "maximum": 9007199254740991,
      +            "minimum": 0,
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "key",
      +          "label",
      +          "value",
      +          "tone"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "detail": {
      +      "type": "string"
      +    },
      +    "headline": {
      +      "type": "string"
      +    },
      +    "kind": {
      +      "enum": [
      +        "html",
      +        "css",
      +        "seo",
      +        "schema",
      +        "links",
      +        "report"
      +      ],
      +      "type": "string"
      +    },
      +    "next_action": {
      +      "type": "string"
      +    },
      +    "shown": {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "status": {
      +      "enum": [
      +        "passed",
      +        "needs_attention",
      +        "partial",
      +        "failed",
      +        "not_applicable"
      +      ],
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "total": {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "status",
      +    "title",
      +    "headline",
      +    "detail",
      +    "total",
      +    "shown",
      +    "truncated",
      +    "counts"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "errors"
      -]New value: +[
      +  "errors",
      +  "overview"
      +]
  5. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior; the description reinforces the last of these by saying it runs inside the Worker without an external service, which adds explanatory context. It does not cover validation strictness, how many messages are returned, or behavior at the 200k character limit, so the added behavioral value is modest.

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?

Two short sentences, front-loaded with the usage condition and followed by the mechanism and result. No filler, though the phrase 'without contacting an external service' could be tightened to a few words.

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?

For a one-parameter, read-only validator with an output schema, the description supplies the trigger and the execution model, which is enough for correct invocation. Return-value details are rightly left to the output schema.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines 'css' as raw CSS source including its length bounds. The description restates the input type but adds no format or syntax guidance beyond the schema, which matches the baseline for a fully documented parameter.

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 names a specific verb and resource ('Parses' raw CSS source) and states the outcome ('returns syntax messages'), which differentiates it from a generic validator. It does not explicitly distinguish itself from the sibling validate_html, so it stops short of a 5.

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?

The trigger condition 'Use this when raw CSS source is supplied' gives an implied when-to-use, which is adequate for a single-purpose validator. There is no mention of when not to use it or of the sibling alternatives (validate_html, validate_schema_markup), so routing must be inferred.

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.

Resources