Skip to main content
Glama

Delete blueprint

delete_blueprint
DestructiveIdempotent

Permanently removes a blueprint by ID; deletion is irreversible, so confirm the ID with get_blueprint or list_blueprints first.

Instructions

Permanently delete one of your blueprints. It cannot be restored. Confirm the id with get_blueprint or list_blueprints first.

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

Input Schema

NameRequiredDescriptionDefault
idYesBlueprint id, e.g. bp_clx1abc.

Output Schema

NameRequiredDescriptionDefault
messageNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / id / description
      Previous value: -"ID of the blueprint to delete"New value: +"Blueprint id, e.g. bp_clx1abc."
    • addedInput schema / properties / id / maxLength
      Added value: +128
    • addedInput schema / properties / id / pattern
      Added value: +"^[A-Za-z0-9][A-Za-z0-9_-]{0,127}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds the crucial detail that deletion is permanent and unrecoverable, plus a verification step. It does not mention permission requirements or what happens to dependent objects, so it is not fully exhaustive.

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?

Three short sentences: what it does, the irreversibility warning, then the precondition. Front-loaded with the action and zero 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 single-parameter destructive tool with rich annotations and an output schema, the description covers the essential facts: permanence, no restore, and id verification. Only permission/authorization expectations and effects on related resources 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?

Schema coverage is 100% and the id format is already documented, so the baseline is 3. The description adds real value by telling the agent where to source a valid id (get_blueprint / list_blueprints), which the schema does not say.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Permanently delete one of your blueprints') and, by naming get_blueprint and list_blueprints, implicitly separates itself from the read-side siblings and from delete_hierarchy. An agent can identify the operation without opening the schema.

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?

Gives a concrete precondition — verify the id with get_blueprint or list_blueprints before calling — which is exactly the guidance needed for an irreversible delete. It stops short of stating when-not-to-use or what to do if the id is stale/not found.

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