Skip to main content
Glama
Sign In
Site Studio

Site Studio

by ToolsEnabled
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

web_css_set

Set one CSS rule in a stylesheet by supplying a selector and declarations. Revision validation blocks stale writes; re-read required.

Instructions

Set one stylesheet rule in a CSS file. declarations is the rule body, for example "color: red; margin: 0".

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": {
      "file_id": "<file_id>",
      "selector": "<selector>",
      "declarations": "<declarations>",
      "expected_rev": "<expected_rev>"
    },
    "name": "web_css_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesCSS file id.
selectorYesFull selector text.
declarationsYesDeclaration list without braces.
expected_revYesRevision returned by your most recent read. Stale revisions refuse; read again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states that a rule is set but does not disclose permissions required, whether existing rules are overwritten, what happens on stale revisions (beyond the schema), or any error behavior. This is a significant gap for a mutation tool.

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 description is two sentences, front-loads the core action, and includes a concrete example without any wasted words. Every sentence earns its place.

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

Completeness2/5

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

Given a mutation tool with no annotations and no output schema, the description is too thin. It omits revision semantics, overwrite behavior, error handling, and return information that an agent would need to call it confidently, even though the schema covers parameter details.

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%, so the baseline is 3. The description adds a useful example for the declarations parameter ("color: red; margin: 0"), which slightly clarifies format beyond the schema, but it does not elaborate on selector, file_id, or expected_rev.

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 states a specific verb (Set) and resource (one stylesheet rule in a CSS file), making the tool's purpose clear. However, it does not distinguish this from sibling tools like web_css or web_set_text, so it falls 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 Guidelines2/5

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

The description gives no guidance about when to use this tool versus alternatives such as web_css or web_set_text, nor does it mention prerequisites or exclusions. Usage is only implied by the verb and resource.

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