Skip to main content
Glama

delete_script

Destructive

Delete a saved script by name to remove unused or outdated automation scripts from tether's browser-automation workflow.

Instructions

Delete a saved script.

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": "delete_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, so the risk profile is known, but the description adds nothing beyond that — it does not say whether the deletion is permanent, whether it works on currently running scripts, or what error occurs if the name is missing. For an irreversible mutation, the description contributes almost no behavioral context.

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?

A single short sentence with no waste, but it is under-specified rather than efficient; there is no structure beyond the minimal statement of action.

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?

For a destructive single-parameter tool with no output schema and no parameter documentation, the description should confirm permanence, identifier format, and failure behavior. None of that is present, leaving the definition thin relative to the tool's risk.

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?

There is one required parameter, name, with 0% schema description coverage, so the description carries the burden of explaining it — yet it only implies the name identifies a saved script. It does not state whether the name must match exactly, is case-sensitive, or is the same identifier returned by list_scripts.

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?

Specific verb plus resource ("Delete a saved script"), which clearly distinguishes it from siblings like get_script, run_script, and save_script. It does not explicitly name those alternatives, but the verb-resource pairing 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?

The description gives no when-to-use context, no prerequisites, and no pointer to alternatives such as save_script or get_script. An agent must infer from the verb alone that this is the removal path for a persisted script.

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