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

scratch-unified-mcp

by blessed0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sb3 Set Comment

sb3_set_comment

Edit an existing Scratch sprite comment by passing its comment ID and new text to update the comment content directly.

Instructions

Edit a sprite comment. (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": {
      "comment_id": "<comment_id>",
      "text": "<text>"
    },
    "name": "sb3_set_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
comment_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Edit' implies mutation, but the description does not mention permissions, reversibility, error behavior for non-existent comments, or what 'proxied' means. This is a significant gap for a write operation.

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

Conciseness2/5

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

The description is only one sentence, but this is under-specification rather than efficient conciseness. It omits critical context and does not earn its brevity because it leaves the agent without enough information to use the tool correctly.

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 simple two-parameter edit tool, the description still lacks essential context: it does not mention what 'proxied' implies, whether a sprite must be selected, how errors are surfaced, or what the output schema returns. Given the zero-coverage schema and no annotations, this is incomplete.

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 adds no information about the parameters. It does not explain that comment_id identifies the target comment or that text is the new content, nor any constraints or formats. The parameter names are self-explanatory, but the description does not compensate for the missing schema field descriptions.

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 a clear verb ('Edit') and resource ('a sprite comment'), making the core action understandable. However, it does not differentiate from closely related sibling tools like sb3_add_comment or sb3_remove_comment, and the parenthetical '(proxied)' is cryptic.

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 guidance on when to use this tool versus alternatives, no prerequisites (e.g., requiring a comment ID or an open project), and no indication of context where this is appropriate. The description simply states what it does without any situational framing.

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