Skip to main content
Glama

remove_layer

Remove a named layer while preserving its connection for reuse by default, or set destroy=true to permanently destroy the connection.

Instructions

移出命名层(缺省连接保留在指纹缓存——再建同层零成本;destroy=true 才真销毁连接)。

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

Input Schema

NameRequiredDescriptionDefault
nameYes层名
destroyNo真销毁连接(缺省 false=保留可复用)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose a genuinely non-obvious behavior: connections are retained in the fingerprint cache by default and re-creating the same layer is zero-cost. It also flags that destroy=true is a real, irreversible destruction. It omits edge cases such as removing a layer that does not exist and what the call returns.

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 sentence with the core action front-loaded and the destructive caveat attached parenthetically. Dense but zero waste; the nested parentheses make the destroy semantics slightly harder to scan, which keeps it from a 5.

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 simple two-parameter tool with no annotations and no output schema, the description covers the important caller-facing behavior (cache retention vs true destruction). Missing only failure/return behavior, which is minor at this complexity.

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 coverage is 100% and both parameters are already documented (name = layer name, destroy = true destroy with default false). The description adds the consequence of destroy=false (cached, free to recreate), which goes slightly beyond the schema's "保留可复用", but largely restates structured data, so baseline 3 applies.

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?

Names a specific verb and resource ("移出命名层" = evict a named layer) and immediately clarifies that the operation is registry-level unless destroy=true. An agent understands what the tool does without opening the schema. It does not explicitly differentiate itself from siblings such as list_layers, so it stops short of a 5.

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 implied by the operation itself, and the description gives useful decision guidance for the destroy flag (default keeps the connection reusable, destroy=true really destroys). However, it names no alternative tool or condition for when removal is the wrong choice versus other layer/connection operations.

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