Skip to main content
Glama

Viral Manager

by com.viral-managers
OverviewDiscussionsAdmin

move_assignment_to_folder

Idempotent

Move one or several existing assignments into a folder (or out of any folder). Attaching the crew that works on them is a separate step: assign_crew.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderYesDestination folder (id, name or full path), or 'none' to remove them from their folder
assignment_idNoOne assignment id (from list_assignments). Use assignment_ids to move several.
assignment_idsNoSeveral assignment ids to move in one call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / assignment_id / default
      Added value: +""
    • changedInput schema / properties / assignment_id / description
      Previous value: -"Assignment id (from list_assignments)"New value: +"One assignment id (from list_assignments). Use assignment_ids to move several."
    • addedInput schema / properties / assignment_ids
      Added value: +{
+  "default": [],
+  "description": "Several assignment ids to move in one call",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / folder / description
      Previous value: -"Destination folder (id, name or full path), or 'none' to remove it from its folder"New value: +"Destination folder (id, name or full path), or 'none' to remove them from their folder"
    • changedInput schema / required
      Previous value: -[
-  "assignment_id",
-  "folder"
-]New value: +[
+  "folder"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With annotations declaring readOnlyHint=false and destructiveHint=false, the description's explicit note that 'out of any folder' removal is part of this tool's behavior adds useful nuance. It also implies the operation is non-destructive, aligning with the annotations, but does not detail failure modes or permissions.

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

Conciseness5/5

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

Two concise sentences front-load the purpose and immediately address the most common fatal ambiguity (moving out of a folder vs deleting). There is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with rich annotations (idempotentHint=true, destructiveHint=false) and complete schema coverage, the description covers the essential behavioral nuance and sibling disambiguation. It could mention what happens when an assignment is moved over an existing folder, but this is not necessary for basic invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100%, with clear descriptions for folder, assignment_id, and assignment_ids. The description adds minimal value beyond the schema, though the phrase 'one or several assignments' reinforces the singular/plural parameter distinction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific action verb ('Move') and a clear resource ('existing assignments') and destination ('folder'), explicitly noting the tool can also move assignments out of a folder. This differentiates it cleanly from sibling tools like assign_crew.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states the core use case (move into or out of a folder) and names the sibling tool to use for the adjacent task ('Attaching the crew... is a separate step: assign_crew'). This tells the agent when not to use this tool, which is strong guidance.

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

All Viral Manager toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources