spy_install_packageInstall a Python package via pip and convert it into Scratch blocks, enabling Python libraries to be used in Scratch projects directly.
pip install a package and turn it into blocks.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
| 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?
No annotations are provided, so the description must carry full behavioral disclosure. It only says 'pip install a package and turn it into blocks' but does not disclose side effects such as network access, project mutation, package overwrites, or failure behavior.
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 a single concise sentence with no filler, and the core pip-install action is front-loaded. Terseness, however, leads to ambiguity around what 'blocks' means.
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?
Although the tool has only one parameter and an output schema, the description omits important context: what happens after installation, whether the current project is modified, how 'blocks' relate to the project, and what the output represents. An agent would still need to investigate before invoking confidently.
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 implies that 'name' refers to a pip-installable package, which adds some meaning beyond the bare string type, but it does not explain name format, version constraints, or whether the package must already be available.
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 concrete action: pip-install a package and transform it into blocks. However, 'blocks' is undefined and the relationship to sibling tools like spy_add_package_blocks or spy_remove_package_blocks is not clarified, so the tool's exact role is only partially clear.
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 such as spy_list_packages or spy_add_package_blocks. There is no mention of prerequisites, like having a project open, or when installation would be unnecessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.