NEXUS AGI

Delete procedure

delete_procedure

DestructiveIdempotent

Permanently delete one stored procedure and its steps. Destructive and irreversible: there is no undo or trash, and agents that relied on it will no longer get it from match_procedures.

Intended for procedures that are wrong or obsolete. update_procedure
fixes steps or tags without deleting, and record_procedure_usage with
success=False lowers the success rate of a procedure that fails only
sometimes. get_procedure shows the procedure before it is deleted.
Returns {"deleted": true}; an unknown UUID returns a not-found error.

Args:
    proc_id: UUID of the procedure to delete, as returned by
        get_procedure, match_procedures or list_procedures.

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

Input Schema

Name	Required	Description	Default
`proc_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 8, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already indicate destructive and idempotent, but the description adds critical context: permanent deletion with no undo/trash, downstream effect on match_procedures, return value, and unknown-UUID error behavior. It enhances rather than contradicts the annotations.

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?

Front-loads the destructive nature and irreversible consequence, then provides alternatives and parameter guidance. Every sentence adds useful information without bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description includes the return shape ({"deleted": true}) and the not-found error case. Combined with annotations and clear parameter provenance, an agent has everything needed to call this correctly.

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 description coverage is 0%, so the description carries the burden for the single proc_id parameter. It specifies the UUID format and where to obtain it (get_procedure, match_procedures, list_procedures), which is meaningful beyond the bare schema.

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 stored procedure and its steps") and clearly distinguishes the action from alternatives. The agent can tell exactly what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states intended use ("procedures that are wrong or obsolete") and names alternatives with conditions: update_procedure for fixes, record_procedure_usage with success=False for intermittent failures, and get_procedure for inspection. This is strong routing guidance.

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

All NEXUS AGI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?