vs-token-safer

Overview Schema Source Related Servers Discussions Admin

rename

Rename a symbol across the project with semantic references. Preview affected files first, then apply to write changes.

Instructions

Rename the symbol at a 0-based position project-wide (semantic — every reference, not a sed). PREVIEW by default (affected file:line); apply=true writes. Use instead of editing call sites by hand.

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": {
      "path": "<path>",
      "line": "<line>",
      "character": "<character>",
      "newName": "<newName>"
    },
    "name": "rename"
  }
}

Input Schema

Name	Required	Description
`line`	Yes	0-based line.
`path`	Yes	Source file containing the symbol.
`apply`	No	Write to disk (default false = preview).
`backend`	No
`newName`	Yes	New name.
`character`	Yes	0-based column.
`maxResults`	No
`projectPath`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.37.3Jun 23, 2026

changedInput schema / properties / apply / description

Previous value: -"Write the edits to disk (default false = preview only)."New value: +"Write to disk (default false = preview)."

removedInput schema / properties / backend / description
```
Removed value: -"Backend override; auto-detected."
```

changedInput schema / properties / character / description

Previous value: -"0-based character/column of the symbol."New value: +"0-based column."

changedInput schema / properties / line / description

Previous value: -"0-based line of the symbol."New value: +"0-based line."

removedInput schema / properties / maxResults / description
```
Removed value: -"Result cap (60)."
```

changedInput schema / properties / newName / description

Previous value: -"New name for the symbol."New value: +"New name."

removedInput schema / properties / projectPath / description
```
Removed value: -"Project root (cwd)."
```

Changed3 schema fields changedv0.29.2Jun 18, 2026

changedInput schema / properties / backend / description

Previous value: -"clangd|roslyn|typescript|pyright (auto)."New value: +"Backend override; auto-detected."

changedInput schema / properties / maxResults / description

Previous value: -"Result cap (default 60)."New value: +"Result cap (60)."

changedInput schema / properties / projectPath / description

Previous value: -"Project root (default cwd)."New value: +"Project root (cwd)."

Changed3 schema fields changedv1.0.3Jun 18, 2026
- addedInput schema / properties / backend / description
```
Added value: +"clangd|roslyn|typescript|pyright (auto)."
```
- addedInput schema / properties / maxResults / description
```
Added value: +"Result cap (default 60)."
```
- addedInput schema / properties / projectPath / description
```
Added value: +"Project root (default cwd)."
```
First observedJun 17, 2026

TDQS

A4.3/5.0

Behavior5/5

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

No annotations provided, but the description fully discloses key behaviors: default preview mode showing affected file:line, and apply=true to write. It also clarifies semantic scope (every reference).

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 sentences that are front-loaded with the core purpose and behavior. Every sentence adds essential information without redundancy.

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 explains the main workflow (preview vs. apply) and scope but lacks output format details and does not cover optional parameters. No annotations or output schema exist, so more completeness would be beneficial, but core functionality is clear.

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 63% (5 of 8 parameters described in schema). The description adds the preview/apply behavior to the apply parameter but does not explain projectPath, backend, or maxResults. It refers to 0-based position, which matches schema descriptions of line and character.

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 renames a symbol at a 0-based position project-wide, emphasizing semantic rename (every reference) and distinguishing from a simple sed replacement.

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 explicitly recommends using this tool 'instead of editing call sites by hand,' providing a clear usage context. However, it does not mention when not to use or compare with sibling tools like replace_symbol_body or safe_delete.

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

Deploy Server