Skip to main content
Glama

delete_schema

Destructive

Permanently remove an agent configuration schema to deactivate its behavior and tools, preventing the agent from using them.

Instructions

Permanently remove an agent configuration schema. Its behavior or tool will no longer be available to the agent.

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

Input Schema

NameRequiredDescriptionDefault
schema_idYesUUID of the schema to deactivate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / schema_id / description
      Previous value: -"UUID do schema a desativar"New value: +"UUID of the schema to deactivate"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the destructive profile is largely covered. The description adds real value by stating the downstream effect (the agent loses that behavior/tool), but it does not address confirmation, cascading effects on agents currently using the schema, or recoverability.

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?

Two short sentences, front-loaded with the destructive verb and resource, then the consequence. Nothing is wasted or redundant.

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 single-parameter destructive tool whose annotations already declare destructiveness and non-idempotency, the description covers purpose and outcome adequately. What remains missing is the impact on live agents and the temporary-disable alternative, both minor for a tool of this size.

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 100% for the single schema_id parameter, so the schema already carries the semantics and the baseline of 3 applies. The description adds nothing about identifier format or behavior on invalid IDs.

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?

States a specific verb and resource ('Permanently remove an agent configuration schema') and adds the consequence that its behavior or tool becomes unavailable. It clearly marks the operation as terminal, though it does not name a sibling like toggle_schema for the non-destructive alternative.

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?

The word 'permanently' implies this is the terminal option rather than a reversible disable, which gives implicit guidance. However, there is no explicit when-to-use, when-not-to-use, or named alternative for temporarily disabling a schema.

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

Deploy Server

Other Tools