Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_semantic_edit_apply

MANAGER EDIT: replace exactly one prepared, hash-bound range.

Instructions

MANAGER EDIT: replace exactly one prepared, hash-bound range.

new replaces the WHOLE prepared range; re-emit every line you keep. allow_escape_level_change: true only for an intentional regex/escape fix.

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": {
      "target_id": "<target_id>",
      "new": "<new>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "aiworkhub_manager_semantic_edit_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
newYesReplacement text for the WHOLE prepared range; re-emit every line you keep.
target_idYesTarget id returned by aiworkhub_manager_semantic_edit_prepare for the range being replaced.
idempotency_keyYesCaller-chosen key; replaying the same key with the same content is a no-op.
allow_escape_level_changeNotrue only for an intentional regex/escape fix; otherwise a re-emitted line whose backslash level changed is refused.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.12.67
    • addedInput schema / properties / allow_escape_level_change / description
      Added value: +"true only for an intentional regex/escape fix; otherwise a re-emitted line whose backslash level changed is refused."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Caller-chosen key; replaying the same key with the same content is a no-op."
    • addedInput schema / properties / new / description
      Added value: +"Replacement text for the WHOLE prepared range; re-emit every line you keep."
    • addedInput schema / properties / target_id / description
      Added value: +"Target id returned by aiworkhub_manager_semantic_edit_prepare for the range being replaced."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's contribution is the hash-bound single-range constraint, the whole-range replacement obligation, and the escape-level refusal behavior. Those are real behavioral details beyond the annotations, though recovery behavior on refusal is unstated.

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 short sentences, front-loaded with the core action and the most error-prone constraint (re-emit every kept line). No filler.

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?

An output schema exists, so return values need no explanation, and the mutation semantics, scope, and escape caveat are covered. The missing piece is the prepare-then-apply workflow and idempotency behavior, which the description only gestures at.

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% and each parameter is already documented in the schema, so the description largely echoes 'new replaces the WHOLE prepared range' and the escape flag rule. Useful reinforcement, but per the high-coverage baseline this is a 3.

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?

States a specific verb and resource: 'replace exactly one prepared, hash-bound range.' It also implies the prepare prerequisite, which differentiates it from aiworkhub_manager_semantic_edit_prepare. It does not explicitly name the sibling, keeping it below a 5.

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?

Explains when to use it (on a prepared range) and gives a conditional rule for allow_escape_level_change ('true only for an intentional regex/escape fix'). It stops short of naming prepare as the mandatory preceding call or saying what to do on refusal.

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