Skip to main content
Glama

list_layers

Lists all named execution layers with chain, state, effective user, and default markers; flags dead or degraded layers so they can be rebuilt after removal.

Instructions

列出全部命名层(链路/状态/有效用户/默认层标记)。死层/退化层有警示标注(removeLayer 后按原参数重建)。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It adds genuine behavioral value by stating that dead/degraded layers are marked with warnings and sketching the remediation workflow (remove then recreate with original parameters), but it never states that the call is read-only and side-effect free, nor anything about ordering, result volume, or failure behavior.

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 compact sentences with the resource definition front-loaded and the warning/remediation detail second. The parenthetical enumerations are dense but each item adds information; nothing reads as filler.

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?

For a zero-parameter listing tool with no output schema, the description does the necessary work of sketching what comes back (named layers by category) and how anomalies appear (warning markers). It is close to complete; only the read-only nature and any ordering or volume expectations are left unstated.

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 beyond what the empty schema already conveys. The baseline of 4 applies, and the description correctly avoids inventing parameter semantics.

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 opens with a specific verb+resource ('列出全部命名层') and enumerates the layer categories returned (链路/状态/有效用户/默认层标记), which makes the tool immediately distinguishable from siblings like remove_layer or edit_file. It stops short of naming a sibling it must not be confused with, so it is clear but not maximally differentiated.

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?

Usage is only implied: it is evidently the enumeration tool to call before acting on layers. The second sentence does give an actionable follow-up path (after removeLayer, rebuild with the original parameters), which points at a concrete alternative, but there is no explicit statement of when to use this versus other discovery tools or of any preconditions.

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