Skip to main content
Glama
mcpware

claude-code-organizer

list_destinations

Shows where a Claude Code item can be moved within the scope hierarchy to organize your development environment.

Instructions

List valid destination scopes for a specific item. Shows where this item can be moved to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesCategory of item
nameYesName of the item
scopeIdYesCurrent scope ID of the item

Implementation Reference

  • The application fetches available move destinations by querying the /api/destinations endpoint. While the tool name "list_destinations" was requested, this code interacts with the `/api/destinations` endpoint, which is the functional equivalent.
    async function openMoveModal(item) {
      const res = await fetchJson(`/api/destinations?path=${encodeURIComponent(item.path)}&category=${encodeURIComponent(item.category)}&name=${encodeURIComponent(item.name)}`);
      if (!res.ok) {
        toast(res.error, true);
        return;
      }
    
      const listEl = document.getElementById("moveDestList");
      const ordered = buildOrderedScopeEntries(res.destinations, res.currentScopeId);
      let selectedDest = null;
    
      listEl.innerHTML = ordered.map(renderDestinationRow).join("");
    
      listEl.querySelectorAll(".dest").forEach((entry) => {
        if (entry.classList.contains("cur")) return;
        entry.addEventListener("click", () => {
          listEl.querySelectorAll(".dest").forEach((node) => node.classList.remove("sel"));
          entry.classList.add("sel");
          selectedDest = entry.dataset.scopeId;
          document.getElementById("moveConfirm").disabled = false;
        });
      });
    
      document.getElementById("moveConfirm").disabled = true;
      document.getElementById("moveConfirm").onclick = async () => {
        if (!selectedDest) return;
        closeMoveModal();
        if (item.locked) {
          // Locked item — generate CC prompt instead of API call
          const destScope = getScopeById(selectedDest);
          const destName = destScope?.name || selectedDest;
          const prompt = `I want to move this Claude Code ${item.category} to a different scope.\n\nItem: "${item.name}"\nCurrent path: ${item.path}\nMove to scope: ${destName}\n\nBefore moving:\n1. Read the file and understand what it does\n2. Determine the correct destination path for the "${destName}" scope\n3. Check if a ${item.category} with the same name already exists at the destination\n4. Explain what will change — which projects will gain or lose access to this ${item.category}\n5. Warn me about any potential conflicts or breaking changes\n6. Only move the file after I confirm`;
          navigator.clipboard.writeText(prompt).then(() => {
            toast("Move prompt copied! Paste to Claude Code in your terminal.");
          });
        } else {
          await doMove(item, selectedDest);
        }
      };
    
      document.getElementById("moveModal").classList.remove("hidden");
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it clarifies the operation is a read (listing), it omits critical details such as the return format (what constitutes a 'destination scope'), error handling if the item is not found, or whether the results are cached or real-time.

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?

The description consists of two efficient sentences with zero wasted words. The first sentence defines the operation, and the second provides immediate utility context. It is appropriately front-loaded and sized for the tool's complexity.

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

Completeness3/5

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

Given the tool has only three simple parameters and no output schema, the description adequately covers the primary purpose. However, it stops short of describing the return structure or behavioral edge cases. With no annotations to provide safety hints, the description meets minimum viability but leaves gaps in the agent's understanding of the output.

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?

Schema description coverage is 100%, with all three parameters (category, name, scopeId) fully documented in the schema. The description mentions 'specific item' which contextualizes that the parameters identify an entity, but does not add semantic detail (syntax examples, format constraints) beyond what the schema already provides. Baseline 3 is appropriate.

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

Purpose4/5

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

The description provides a specific verb ('List') and resource ('valid destination scopes') and clearly identifies the target ('specific item'). It implicitly distinguishes from move_item by clarifying this only shows where an item 'can be moved to' rather than performing the move itself, though it does not explicitly name the sibling tool.

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

Usage Guidelines3/5

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

The phrase 'Shows where this item can be moved to' implies the tool is used to evaluate potential move targets before invoking a move operation. However, it lacks explicit guidance on when to use this versus alternatives (e.g., 'Call this before move_item to validate destinations'), leaving the workflow somewhat implied rather than stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcpware/claude-code-organizer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server