scratch-unified-mcp

by blessed0x

Overview Schema Source Related Servers Discussions Admin

Python

Local

Sb3 Set Sprite

sb3_set_sprite

Set sprite properties such as position and size by providing a JSON object string.

Instructions

Set sprite props; props is a JSON object string (x, y, size, ...). (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": {
      "name": "<name>"
    },
    "name": "sb3_set_sprite"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`props`	No		{}

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 19, 2026

TDQS

C2.7/5.0

Behavior2/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. It reveals that the operation is 'proxied' and that props is a JSON object string, but it does not explain side effects, persistence, mutation behavior, or whether existing props are overwritten or merged.

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

Conciseness4/5

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

The description is compact and front-loaded with the core action and resource. The parenthetical '(proxied)' is cryptic but not wasteful. It earns a strong score for brevity, though it sacrifices explanatory depth.

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 mutation-style tool with no annotations, the description is too thin. It does not explain how the sprite is identified, what properties are valid, how the proxy affects behavior, or what happens after the call. The presence of an output schema reduces the need to describe return values, but key invocation and safety context is still missing.

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%, so the description must compensate. It partially explains the 'props' parameter by specifying it is a JSON object string with fields like x, y, and size, but it does not explain the required 'name' parameter at all, leaving the agent to guess that it identifies the target sprite.

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 specific action ('Set') on a clear resource ('sprite props') and gives examples of the affected properties ('x, y, size'). It is not a tautology and is clear enough for an agent to understand the basic operation. However, it does not explicitly distinguish itself from closely related siblings like sb3_patch_target or sb3_set_stage.

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 mention of prerequisites, and no exclusion criteria. The agent must infer usage purely from the tool name and the terse description.

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

Deploy Server