Scans a folder to list all .mblock and .sb3 project files, so you can locate the project file you need.
List .mblock/.sb3 projects under a folder. Start here to find a project file.
| Name | Required | Description | Default |
|---|---|---|---|
| root | No | Folder to scan (default: MBLOCK_PROJECTS) |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds minimal behavioral context by defining the file types scanned, but it does not disclose recursion behavior, output format, or ordering. It is adequate but not rich.
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?
Two short sentences, no filler. The core action and resource are front-loaded, and the usage hint is delivered efficiently. Every word earns its place.
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?
For a simple read-only list tool with one optional, fully documented parameter and strong annotations, the description is nearly complete. It could mention the output format (file paths vs names), but the absence is minor given the low complexity and clear purpose.
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 100%: the 'root' parameter is already documented as the folder to scan with a default of MBLOCK_PROJECTS. The description adds no parameter information beyond the schema, so it meets the baseline for fully documented parameters.
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 ('List'), a specific resource ('.mblock/.sb3 projects'), and a scope ('under a folder'). The phrase 'Start here to find a project file' positions it as the discovery/listing tool and distinguishes it from siblings like project-open or project-validate.
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?
'Start here to find a project file' gives clear guidance on when to use this tool: as the entry point for locating projects. It does not explicitly name alternatives or state when not to use it, but the intended context is clear enough for an agent to select it for listing/discovery.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.