Skip to main content
Glama
Sign In
vs-token-safer

vs-token-safer

by JSungMin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

insert_symbol

Insert text next to a named declaration, choosing before or after position, with preview by default for safe editing.

Instructions

Insert text next to a named declaration — position=after (default)|before. The outline gives the point (no Read). PREVIEW by default; apply=true writes. Use instead of Read-then-Edit to add a declaration.

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": {
      "symbol": "<symbol>",
      "text": "<text>"
    },
    "name": "insert_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNo0-based line; disambiguate same-named (optional).
pathNoFile holding the symbol (else resolved via the index).
textYesText to insert (own line).
applyNoWrite to disk (default false = preview).
symbolYesDeclaration to insert next to.
backendNo
positionNo`after` (default) | `before`.
maxResultsNo
projectPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.37.3
    • changedInput schema / properties / apply / description
      Previous value: -"Write 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."
    • removedInput schema / properties / maxResults / description
      Removed value: -"Result cap (60)."
    • changedInput schema / properties / position / description
      Previous value: -"`after` (default) or `before` the declaration."New value: +"`after` (default) | `before`."
    • removedInput schema / properties / projectPath / description
      Removed value: -"Project root (cwd)."
    • changedInput schema / properties / text / description
      Previous value: -"Text to insert (on its own line)."New value: +"Text to insert (own line)."
  2. Changed1 schema field changedv0.35.0
    • changedInput schema / properties / line / description
      Previous value: -"0-based line to disambiguate same-named symbols (optional)."New value: +"0-based line; disambiguate same-named (optional)."
  3. Changed3 schema fields changedv0.29.2
    • 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)."
  4. Addedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Discloses preview mode by default, write when apply=true, and that it uses outline without read step. No annotations provided, so description carries burden well.

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 with key information front-loaded; every clause adds value 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?

No output schema, so description should explain return values or errors, but does not. Lacks details on preview output format and error handling for symbol resolution.

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?

Adds meaning for key parameters (symbol, text, position, apply) but does not describe path, line, projectPath, backend, maxResults beyond schema. Schema coverage 67% so moderate compensation.

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?

Clearly states 'Insert text next to a named declaration' with position option, and distinguishes from siblings like 'Read-then-Edit' and other modification tools.

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?

Explicitly says 'Use instead of Read-then-Edit to add a declaration' and notes preview default vs. apply=true, but does not list when to avoid using it.

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