Skip to main content
Glama

list_cockpit_widgets

Read-only

Catalog for building a custom cockpit with save_cockpit: the available widgets (key, title, description, fields), the classic definition, the default traffic-light thresholds and the allowed range of each threshold.

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_cockpit_widgets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds substantive return-value context beyond that: it discloses the exact payload shape (widget key, title, description, fields) plus default thresholds and allowed ranges, which is what an agent needs to construct a valid cockpit definition.

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?

A single dense sentence with the purpose and the motivating sibling front-loaded, followed by the payload inventory. Every clause carries information, though the list of returned components is slightly comma-heavy and could be broken out for faster scanning.

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?

With no output schema and no parameters, the description must carry the burden of explaining what comes back, and it enumerates the returned catalog contents in enough detail to build a save_cockpit payload. It does not state whether all sections are always present or how thresholds are keyed, a minor gap for a static reference tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly frames the call as argument-free by presenting the tool purely as a reference lookup.

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 identifies the resource precisely (widget catalog: keys, titles, descriptions, fields, classic definition, default traffic-light thresholds and their allowed ranges) and ties it to the sibling it supports, save_cockpit. It stops just short of an explicit verb such as 'returns/lists', relying on the noun 'catalog' to convey the read.

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 'for building a custom cockpit with save_cockpit' gives a clear use context and effectively routes the agent here before calling save_cockpit. It does not contrast with get_cockpit or list_cockpits, and gives no explicit when-not-to-use condition.

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