Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Describe the Theme Studio values

describe_theme_values
Read-onlyIdempotent

What a graph's look can set (see "Theme Studio" in get_guide): the themes, card materials and control families, and every value with its type and range. Filter by surface (Application, Node editor canvas, Nodes, Connections, Dashboard, Cards, Widgets) or group (Colors, Background, Edges, Glow, Shadows).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "describe_theme_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
surfaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the bar is low. The description adds real content beyond that: it discloses what the response contains (values with their type and range) and the axes by which results can be narrowed, which is exactly the behavioral context an agent needs.

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?

Compact: one main clause defining the content followed by a filtering sentence that enumerates valid values. The parenthetical get_guide cross-reference earns its place, though the parenthetical placement slightly interrupts the opening statement.

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?

No output schema exists, and the description compensates by saying the result is every value with its type and range. Combined with the explicit enumerations of surface and group filters, an agent has enough to invoke it correctly; only the meaning of the empty-string default is left implicit.

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

Parameters5/5

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

Schema coverage is 0% (parameters are bare strings titled Group and Surface), so the description carries the full burden and does so by enumerating the accepted surface values (Application, Node editor canvas, Nodes, Connections, Dashboard, Cards, Widgets) and group values (Colors, Background, Edges, Glow, Shadows). That is precisely the semantics the schema omits.

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 resource: the theme values a graph's look can set, broken into themes, card materials, control families, and each value with type and range. This is clearly distinct from siblings like describe_node_type or describe_widget_style, though the description never explicitly contrasts with them.

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?

Implied usage is clear (look up allowed theme values before setting them) and it cross-references get_guide for the Theme Studio concept. However, it never states when to prefer this over describe_widget_style or describe_node_type, nor whether filtering is required or optional.

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