sb3_set_stageSet stage props by providing a JSON object string, enabling direct control over the Scratch project's stage attributes for automated workflows.
Set stage props; props is a JSON object string. (proxied)
| Name | Required | Description | Default |
|---|---|---|---|
| props | No | {} |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the operation is 'proxied' and that props is a JSON object string, but it does not explain side effects, required context, error behavior, or what happens to existing stage settings. The term 'proxied' is left unexplained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and front-loaded, with no wasted words. However, the parenthetical 'proxied' is ambiguous and the brevity contributes to the lack of behavioral context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a mutation tool with no annotationsaging, a single loosely specified parameter, and no usage guidance. An agent would know it can send a JSON object string but not what props to include, making the definition insufficient for reliable invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 does add the key fact that props is a JSON object string rather than an arbitrary string, but it does not describe which properties are valid or expected within that JSON object.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Set stage props', and it clarifies that props is a JSON object string. This clearly identifies what the tool operates on, though it does not enumerate the types of stage props supported.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool versus alternatives like sb3_set_sprite, sb3_patch_target, or sb3_set_variable. The description does not mention any exclusions, prerequisites, or scenarios where another tool should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.