Skip to main content
Glama

get_style

Read-only

Fetch editable CSS for a saved style so you can modify it; imported styles return the full UserCSS file.

Instructions

Read a saved style, to change it. Returns the editable CSS for styles you saved, or the whole UserCSS file for imported ones.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real behavioral detail by explaining that the return payload differs by style origin — editable CSS for user-saved styles versus the entire UserCSS file for imported ones. That distinction matters for anyone consuming the result, and it is not derivable from the schema or annotations.

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 with the core action and the return-value distinction front-loaded; nothing is padding. The phrase 'to change it' is slightly ambiguous (this tool does not change anything) but is efficiently placed.

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

Completeness3/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 usefully covers the two return shapes, which is the most important gap to fill. It leaves open what happens for an unknown name and how the 'name' argument is matched, so an agent could still invoke it with a wrong identifier.

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

Parameters2/5

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

There is a single required parameter, 'name', with 0% schema description coverage, so the description carries the full burden — but it never mentions the parameter or clarifies whether it is a style title, a filename, or an identifier. 'A saved style' gives only the vaguest hint about what the name refers to.

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 specific verb and resource ('Read a saved style') and adds motivating purpose ('to change it'). It implicitly distinguishes itself from the sibling list_styles by addressing a single saved style, though it never names an alternative 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 'to change it' implies the intended workflow: fetch a style before modifying or re-saving it. There is no explicit when-not guidance, no mention of the alternative (e.g. list_styles to discover names), and no stated prerequisite such as knowing a valid style name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.