Skip to main content
Glama
Sign In
scratch-unified-mcp

scratch-unified-mcp

by blessed0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sb3 Delete Variable

sb3_delete_variable

Remove a specified variable from a Scratch project by providing its name and target.

Instructions

Delete a variable. (proxied)

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": {
      "target": "<target>",
      "name": "<name>"
    },
    "name": "sb3_delete_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral burden. It states only that deletion occurs and that it is 'proxied,' but does not disclose irreversibility, effect on the project, permissions, or what happens if the variable does not exist.

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?

The sentence is very short and front-loaded, but the parenthetical 'proxied' is vague and does not clearly earn its place. The brevity is appropriate for the two-parameter operation, but it sacrifices useful detail.

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?

An output schema may cover return values, but an agent still needs context about variable scope, target semantics, and the delete operation's effect on the project. The description is too sparse to fully support correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description gives no meaning for 'target' or 'name' beyond the bare schema. It does not specify that target identifies the sprite/stage scope or what form name should take.

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?

The description states the exact operation: 'Delete a variable.' The verb and resource are specific, and the name distinguishes it from sibling tools like sb3_delete_list and sb3_set_variable, though it does not explicitly contrast with them.

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?

No guidance is provided about when to delete a variable, whether it applies to the current target/sprite, or how this compares with sb3_set_variable or the cloud variable tools. The reader is left to infer scope and prerequisites.

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