Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Describe a widget style

describe_widget_style
Read-onlyIdempotent

Look up one exact stable style ID including its node UI key, read-only/control semantics, material family, unit presentation, GPU support and non-rendered appearance hints.

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

Input Schema

NameRequiredDescriptionDefault
style_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive lookup. The description adds useful context by specifying the returned payload categories, including node UI key, control semantics, material family, GPU support, and appearance hints, which helps the agent understand what it will receive.

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 definition is a single front-loaded sentence with no redundant framing. Every listed item describes the returned information and earns its place.

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?

For a simple one-parameter read-only lookup with rich annotations, the description is adequate but not complete. It lists the categories of information returned, yet without an output schema it does not describe their structure, and it does not explain how to obtain a valid style_id.

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 0%, so the description must carry parameter meaning. It clarifies that the argument is one exact stable ID rather than a name or pattern, but it does not specify the ID format or where the agent should obtain it, leaving a meaningful gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ("Look up") and resource ("one exact stable style ID"), and it enumerates the exact information returned. This distinguishes it from the sibling list_widget_styles, which handles collections rather than one exact ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The phrase "one exact stable style ID" makes the usage context clear: this tool is for resolving a known ID, not for browsing. It does not explicitly name list_widget_styles or state when not to use it, so it falls short of full alternative routing.

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