Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

setEditorDecorations

Idempotent

Apply grouped visual highlights and inline messages to specific lines in a file. Replace all decorations for a group with each call.

Instructions

Place visual decorations (highlights, inline text) on file lines. Grouped by ID; replaces on each call.

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": {
      "id": "<id>",
      "file": "<file>",
      "decorations": "<decorations>"
    },
    "name": "setEditorDecorations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGroup name for decorations (alphanumeric + hyphens)
fileYesAbsolute path to the file to decorate
decorationsYesDecorations to apply

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the idempotentHint annotation, the description adds the key behavioral trait that decorations are replaced on each call, giving the agent a clear understanding of the tool's side effects.

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 redundancy: first sentence states purpose, second explains grouping and replacement. Every word adds value.

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 description covers the core functionality and behavior, and the schema fully documents parameters. It could mention return value or error handling, but given the tool's nature, the description is adequate.

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?

The input schema already provides full 100% coverage with descriptions for all parameters. The description adds no additional semantic detail beyond what the schema offers, so a 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 the tool places visual decorations on file lines and explains grouping by ID with replacement behavior, distinguishing it from sibling tools like clearEditorDecorations.

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

Usage Guidelines4/5

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

The description implies when to use (e.g., to set/replace decorations by ID) but does not explicitly mention when not to use or alternative tools, though the sibling 'clearEditorDecorations' exists.

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