Skip to main content
Glama
Sign In
Site Studio

Site Studio

by ToolsEnabled
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

web_css

Read CSS rules from the current working copy by matching selector text, so you can inspect styles for a selector like .hero before editing.

Instructions

Read CSS rules whose selector contains the requested text, from the current working copy.

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": {
      "selector": "<selector>"
    },
    "name": "web_css"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idNoOptional CSS file id.
selectorYesSelector text, for example .hero.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that this is a read operation against the working copy, which is useful, but says nothing about return shape, ordering, pagination, or how unmatched selectors behave. Adequate but not rich.

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?

A single front-loaded sentence with no filler; the read scope and matching rule are stated immediately.

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 two-parameter read tool with no output schema, the description covers the operation and its matching semantics, and the schema documents file_id. It could say more about what the read returns, but nothing critical to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds genuine meaning beyond the schema by specifying that the selector is matched by substring containment ('contains the requested text') rather than exact match, which the schema's '.hero' example does not convey.

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?

States a clear verb and resource: 'Read CSS rules whose selector contains the requested text.' The read-only framing distinguishes it implicitly from web_css_set, and the substring matching is a specific scope, but no sibling is named explicitly.

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 phrase 'from the current working copy' gives a hint about context, and the substring-selector framing implies when it applies, but there is no explicit when-to-use/when-not guidance or routing to sibling tools like web_css_set or web_find.

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