Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

getCodeActions

Read-only

Retrieve available code actions like quick fixes and refactorings for a specified range in a file, enabling automated code improvements.

Instructions

Get available code actions (quick fixes, refactorings) for a range in a file.

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>",
      "startLine": "<startLine>",
      "startColumn": "<startColumn>",
      "endLine": "<endLine>",
      "endColumn": "<endColumn>"
    },
    "name": "getCodeActions"
  }
}

Input Schema

NameRequiredDescriptionDefault
endLineYesEnd line (1-based)
filePathYesWorkspace or absolute path
endColumnYesEnd column (1-based)
startLineYesStart line (1-based)
startColumnYesStart column (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The description aligns with the readOnlyHint annotation (true) by describing a read operation. However, it adds no additional behavioral context beyond what annotations provide (e.g., no mention of side effects or analysis triggers). No contradiction.

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?

One concise sentence (13 words) that clearly states the purpose with no unnecessary words or repetition. Excellent front-loading.

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?

The tool has 5 required params, no output schema, and a simple read operation. The description is sufficient for the agent to understand the basic purpose, though it does not specify the return format (e.g., list of action names). Given the simplicity, this is a minor gap.

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% for all 5 parameters. The description only mentions 'range in a file', which does not add meaning beyond the schema descriptions (e.g., line/column numbers). Baseline 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 explicitly states the verb 'Get', the resource 'code actions', and the scope 'for a range in a file'. It clearly distinguishes from siblings like applyCodeAction (which applies the action) and previewCodeAction (which previews).

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 does not provide guidance on when to use this tool versus alternatives (e.g., applyCodeAction, previewCodeAction). The context is implied but no explicit when-to or when-not-to guidance.

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