Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

organizeImports

DestructiveIdempotent

Sort and organize import statements in a workspace file using VS Code extension or fallback tools like Biome or Prettier.

Instructions

Organize/sort imports in workspace file. Uses VS Code ext when connected; falls back to Biome or Prettier.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filePath": "<filePath>"
    },
    "name": "organizeImports"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesFile to organize imports in (relative or absolute path)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations provide destructiveHint and idempotentHint. The description adds value by explaining the fallback mechanism (VS Code ext when connected, else Biome/Prettier), which goes beyond annotation information. However, it does not detail what exactly happens (e.g., does it remove unused imports? only sort?).

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 with no unnecessary words. The key information (what it does and fallback behavior) is front-loaded.

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?

The description covers the fallback strategy but lacks details on exactly what 'organize/sort' entails (e.g., sorting order, removal of unused imports). No output schema is provided, so the description should clarify expected results. It is adequate but not fully complete.

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 coverage is 100% with a clear description for filePath. The description adds no additional parameter semantics beyond the schema, so baseline score of 3 is appropriate.

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 clearly states 'Organize/sort imports in workspace file', specifying the verb (organize/sort) and resource (imports in workspace file). It distinguishes itself from sibling tools like formatDocument or fixAllLintErrors by focusing specifically on imports.

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 description mentions fallback behavior (VS Code ext vs Biome/Prettier), but does not explicitly state when to use this tool over alternatives like formatAndSave or fixAllLintErrors. The usage context is implied rather than explicitly guided.

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

Deploy Server

Other Tools