Skip to main content
Glama

LazyAnalysis — AI Solution Composer

List indicator and control styles

list_widget_styles
Read-onlyIdempotent

Discover native indicator/control style IDs, read-only vs interactive semantics, saved UI setting keys and display modes. Reports coarse style-family appearance hints and configurable display-only engineering unit fields; no rendered previews or dimensional math. Use before create_graph when selecting premium radar, analog/VU meters, LED, rotary knob or slider materials. Pages max 100 results.

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": "list_widget_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
familyNo
offsetNo
searchNo
gpu_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value beyond that: explicit non-goals ("no rendered previews or dimensional math"), the nature of what is returned (coarse style-family hints, configurable display-only unit fields), and a pagination ceiling of 100 results. It still does not mention ordering or what happens when offset exceeds the match count.

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?

Four sentences, front-loaded with what is discoverable, then non-goals, then the routing instruction, then the pagination constraint. Every sentence carries content, though phrases like "coarse style-family appearance hints" and "configurable display-only engineering unit fields" are denser than they need to be.

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?

As a read-only listing tool with no output schema, the behavioral picture is reasonably complete and annotations handle the safety profile. The major residual gap is parameter meaning: with six parameters at zero schema coverage, an agent cannot confidently construct filtered or paginated calls from this description alone.

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?

Schema description coverage is 0% across six parameters, so the description carries the full explanatory burden and largely fails to meet it. It hints implicitly at kind (radar/meter/LED/knob/slider), family ("style-family appearance hints"), and limit ("Pages max 100 results"), but search, offset, and gpu_only are never addressed anywhere.

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 uses a specific verb ("Discover") with a concrete resource set: native indicator/control style IDs, read-only vs interactive semantics, saved UI setting keys, display modes, and engineering unit fields. This clearly distinguishes it as an enumeration tool rather than a single-item lookup, though it never names the natural follow-on sibling (describe_widget_style) for detail on one style.

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?

It states an explicit usage moment: "Use before create_graph when selecting premium radar, analog/VU meters, LED, rotary knob or slider materials." That is a real when-to-use condition tied to a named sibling. It stops short of stating when NOT to use it (e.g., when you already have a style ID and should call describe_widget_style instead).

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