bin_move
Move selected folders or bins into a target bin to reorganize your project media.
Instructions
Move bins into another bin.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| folder_handles | Yes |
Move selected folders or bins into a target bin to reorganize your project media.
Move bins into another bin.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| folder_handles | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It only says 'Move bins into another bin', which implies a non-destructive move, but does not disclose whether the original bin is deleted, if contents are recursively moved, or required permissions. The transparency is minimal.
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?
While the description is very concise (one short sentence), it is under-specified. It does not earn its place because it omits critical details. Conciseness should not come at the cost of clarity, so this score reflects the lack of informative content.
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?
Given the tool's complexity (a move operation with two required parameters, no output schema), the description is incomplete. It does not explain return values, side effects (e.g., does it move all nested bins?), or error conditions. The agent lacks sufficient information to use this tool correctly.
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%, meaning the description adds no meaning to the parameters 'folder_handles' and 'target'. The description does not explain what these represent (e.g., IDs, paths), their format, or how they relate to the operation. This is a severe omission.
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 clearly states the verb 'Move' and the resource 'bins into another bin'. It distinguishes from siblings like clip_move or bin_delete by specifying the operation on bins specifically. However, it could be more precise about what constitutes a 'bin' in this context (e.g., folder or container?).
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 provided on when to use this tool versus alternatives like clip_move or bin_set_current. There is no mention of prerequisites, restrictions, or typical use cases. The description lacks actionable context for an AI agent to decide when to invoke this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/irstone-source/resolve-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server