Skip to main content
Glama

delete_machine

Unpairs and deletes a machine from a norc account using its ID, removing it from managed cron jobs and machine oversight.

Instructions

Unpair (delete) a machine.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and provides almost none. "Unpair" hints the machine may only be detached while its jobs/runs persist, yet it also says "delete," leaving unclear whether associated data is destroyed, whether the action is reversible, or what permissions are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two words with zero padding, but the brevity is under-specification rather than tight writing. The action is front-loaded, which is good, but there is no structure beyond the fragment.

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

Completeness2/5

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

A destructive mutation tool with no annotations, no output schema, and an undocumented required identifier—the description should at minimum state permanence, side effects, and the nature of the id. As written, an agent cannot safely predict the consequences of the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter "id" is never explained—there is no statement of what identifier it takes, nor of where an agent obtains one. The description contributes nothing about the parameter.

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?

"Unpair (delete) a machine" states a concrete verb plus resource and glosses the jargon "unpair" with "delete," so an agent knows this removes a machine. It does not contrast explicitly with sibling mutations like rename_machine or delete_job, but the target resource is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no reference to alternatives such as rename_machine for non-destructive changes. The agent must infer that this is the destructive path for a machine.

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