Skip to main content
Glama
mcpware

claude-code-organizer

scan_inventory

Scan Claude Code configurations across all scopes to inventory memories, skills, servers, and settings with file paths and metadata.

Instructions

Scan all Claude Code configurations across every scope (global, workspace, project). Returns memories, skills, MCP servers, hooks, configs, plugins, and plans with their file paths and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The init() function calls the /api/scan endpoint to fetch the inventory data for the UI. The request is named "scan_inventory" by the user prompt, but the implementation is via the /api/scan endpoint in the frontend code.
    async function init() {
      try {
        data = await fetchJson("/api/scan");
        selectedScopeId = getInitialSelectedScopeId();
        initializeScopeState();
        setupUi();
        renderAll();
      } catch (error) {
        document.getElementById("loading").textContent = "Failed to load inventory";
        toast(error?.message || "Failed to load inventory", true);
      }
    }
Behavior4/5

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

No annotations provided, so description carries full burden. Compensates well by comprehensively enumerating return values (7 distinct item types plus file paths/metadata), effectively filling the gap of missing output schema. Does not explicitly state read-only nature or 'scan' performance implications, but the return structure disclosure is substantial.

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 tightly constructed sentences. First establishes operation and scope; second details return values. Every clause earns its place with zero redundancy or generic filler.

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

Completeness5/5

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

Given zero input parameters, no output schema, and no annotations, the description achieves completeness by fully specifying the operation (scan), scope (all scopes), and return structure (detailed enumeration of items with metadata). No critical gaps remain for this tool's complexity level.

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

Parameters4/5

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

Zero parameters present per schema. Per rubric rules, 0 params = baseline 4. Schema coverage is vacuously 100% (no parameters to describe), requiring no additional parameter semantics from description.

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?

Excellent specificity: 'Scan' verb + 'Claude Code configurations' resource + explicit scope enumeration (global, workspace, project). Clearly distinguishes from siblings (delete_item, move_item, list_destinations) by focusing on broad configuration inventory rather than item manipulation.

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?

Provides implicit guidance through scope specification ('across every scope'), suggesting use for comprehensive audits. However, lacks explicit when-to-use/when-not-to-use statements or direct comparison to siblings like delete_item or list_destinations.

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