Skip to main content
Glama
JSungMin

vs-token-safer

by JSungMin
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

find_references

Find every semantic reference to a symbol before editing it, with token-capped file:line results. Use callers/callees or a blast-radius summary to assess impact.

Instructions

Every call site of a symbol (semantic, not grep) — pass symbol (a name); resolves the decl + returns all refs in one call. → capped file:line; detail=file|dir for a blast-radius summary; direction=callers|callees switches to a multi-hop call hierarchy. Use before changing a function.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineNo0-based line.
pathNoSource file (+line/character for an exact position, or with `symbol` to disambiguate an overload).
depthNoCall-hierarchy hops (default 2).
detailNo`file`|`dir` blast-radius summary.
symbolNoSymbol NAME — resolved via the index, no position needed.
backendNo
characterNo0-based column.
directionNocallers|callees call hierarchy.
maxResultsNo
projectPathNo
includeDeclarationNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.37.3
    • removedInput schema / properties / backend / description
      Removed value: -"Backend override; auto-detected."
    • removedInput schema / properties / includeDeclaration / description
      Removed value: -"Include the declaration."
    • removedInput schema / properties / maxResults / description
      Removed value: -"Result cap (60)."
    • changedInput schema / properties / path / description
      Previous value: -"Source file (with line/character for an exact position; or with `symbol` to disambiguate)."New value: +"Source file (+line/character for an exact position, or with `symbol` to disambiguate an overload)."
    • removedInput schema / properties / projectPath / description
      Removed value: -"Project root (cwd)."
    • changedInput schema / properties / symbol / description
      Previous value: -"Symbol NAME — resolved via the index, no position needed (the usual way when editing)."New value: +"Symbol NAME — resolved via the index, no position needed."
  2. Changed3 schema fields changedv0.35.0
    • changedInput schema / properties / depth / description
      Previous value: -"Call-hierarchy hops when direction is set (default 2)."New value: +"Call-hierarchy hops (default 2)."
    • changedInput schema / properties / detail / description
      Previous value: -"`file`|`dir` → blast-radius summary instead of the per-line list."New value: +"`file`|`dir` blast-radius summary."
    • changedInput schema / properties / direction / description
      Previous value: -"callers|callees → multi-hop call hierarchy instead of flat refs."New value: +"callers|callees call hierarchy."
  3. Changed3 schema fields changedv0.34.2
    • changedInput schema / properties / depth / description
      Previous value: -"Call-hierarchy hops when direction is set (default 2; capped by VTS_TRACE_MAX_DEPTH)."New value: +"Call-hierarchy hops when direction is set (default 2)."
    • changedInput schema / properties / detail / description
      Previous value: -"`file` or `dir` → a blast-radius summary (dependents grouped + ranked by ref count) instead of the per-line list; omit for the full list."New value: +"`file`|`dir` → blast-radius summary instead of the per-line list."
    • changedInput schema / properties / direction / description
      Previous value: -"callers | callees → a multi-hop CALL HIERARCHY (who transitively calls this / what it calls) instead of flat references; omit for usages."New value: +"callers|callees → multi-hop call hierarchy instead of flat refs."
  4. Changed2 schema fields changedv0.31.0
    • addedInput schema / properties / depth
      Added value: +{
+  "description": "Call-hierarchy hops when direction is set (default 2; capped by VTS_TRACE_MAX_DEPTH).",
+  "type": "number"
+}
    • addedInput schema / properties / direction
      Added value: +{
+  "description": "callers | callees → a multi-hop CALL HIERARCHY (who transitively calls this / what it calls) instead of flat references; omit for usages.",
+  "type": "string"
+}
  5. Changed4 schema fields changedv0.29.2
    • changedInput schema / properties / backend / description
      Previous value: -"clangd|roslyn|typescript|pyright (auto)."New value: +"Backend override; auto-detected."
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "`file` or `dir` → a blast-radius summary (dependents grouped + ranked by ref count) instead of the per-line list; omit for the full list.",
+  "type": "string"
+}
    • 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)."
  6. Changed8 schema fields changedv1.0.3
    • addedInput schema / properties / backend / description
      Added value: +"clangd|roslyn|typescript|pyright (auto)."
    • changedInput schema / properties / character / description
      Previous value: -"0-based character/column of the symbol position."New value: +"0-based column."
    • changedInput schema / properties / includeDeclaration / description
      Previous value: -"Include the declaration in the results."New value: +"Include the declaration."
    • changedInput schema / properties / line / description
      Previous value: -"0-based line of the symbol position."New value: +"0-based line."
    • addedInput schema / properties / maxResults / description
      Added value: +"Result cap (default 60)."
    • changedInput schema / properties / path / description
      Previous value: -"Source file containing the symbol (with line/character for an exact position; or alongside `symbol` to disambiguate an overload)."New value: +"Source file (with line/character for an exact position; or with `symbol` to disambiguate)."
    • addedInput schema / properties / projectPath / description
      Added value: +"Project root (default cwd)."
    • changedInput schema / properties / symbol / description
      Previous value: -"Symbol NAME to find references of — resolved via the index (no position needed). The usual way to find call sites when editing."New value: +"Symbol NAME — resolved via the index, no position needed (the usual way when editing)."
  7. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries full weight. It mentions resolving declaration, returning all refs in one call, and capping output at file:line. Does not disclose error handling, performance implications, or limitations (e.g., on large projects). Adequate but not thorough.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, packed with information but front-loaded. The first sentence is dense with multiple ideas; could be split for clarity. Nonetheless, no wasted words and all content is relevant.

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?

Given 11 parameters and no output schema, the description covers core functionality and provides a usage hint. However, it omits details on many parameters and does not fully explain return format beyond 'capped file:line'. Incomplete for a complex tool.

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 description coverage is 64%. The description adds meaning for 'symbol' (resolved via index) and 'detail'/'direction' (purpose). But several parameters (includeDeclaration, depth, projectPath, etc.) are not explained in the description, relying on schema. Baseline 3, with modest added value.

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?

Clearly states the tool finds semantic call sites of a symbol, distinguishing from grep. Mentions alternative modes (blast-radius, call hierarchy). However, does not explicitly differentiate from sibling tools like 'search_symbol' or 'goto_definition', leaving some ambiguity.

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?

Provides a clear usage recommendation ('Use before changing a function') and explains alternative modes (detail, direction). Lacks explicit when-not-to-use guidance or comparison to siblings, but the given context is helpful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JSungMin/vs-token-safer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server