Skip to main content
Glama

Find Usages of a Symbol

find_usages
Read-onlyIdempotent

Lists direct users of a C# type, member, or constructor to assess impact before changing or deleting it; covers callers, readers, writers, raisers, subscribers, and test users.

Instructions

List who uses a symbol (direct fan-in); impact_of_change adds closure and risk, calls_external covers external members.

Use it before changing or deleting a symbol, not grep. What is listed depends on resolvedKind: 'type' - the types that reference it (a doc cref too: docCrefOnly), plus markup views; 'method' - its callers, overloads unioned ('overloads'; item 'calls': its own); 'property' or 'field' - its readers and writers; 'event' - its raisers and (un)subscribers; 'enum_member' - its references; 'operator' ('op_Equality') - its uses, casts too; 'constructor' ('Type.Type') - the type's construction and injection sites. Test users included.

Returns symbol, resolvedKind, usedBy (capped envelope: items, count, totalFound, truncated; max 100). An item is {name, file, line}, one per user: file is solution-relative, line where its declaration starts (not the reference); 'files' [{file, line}] for a type declared in several; absent if unknown; users sharing a name add 'fullName' (a type), 'project'. Optional members qualify it: 'note' ahead of the list (an empty or constructor answer, unresolved core references), 'namesakes' (several types share it, unioned), 'collision' (a same-named other kind, not counted), 'viaContract' + 'viaContractNote' (a qualified method's contract or virtual-base callers), 'selfReferences' (users on the member's own type), 'textuallyInvisibleUsers' (users not naming it), 'nearest' (on 'not_found': a close name), 'resourceKeyNote' (markup keys the type; those views: find_resource_usages).

An empty usedBy on a resolved symbol is not proof of dead code: entry points, DI, reflection, source generators and unrecorded markup leave no reference. 'not_found' is not 'undeclared': a delegate type and a qualified or nested type name answer it; 'note' may say why.

Read-only. symbol is case-sensitive. A type takes its simple name. A member takes 'Type.Member' for one type's, or a bare name: that answers for ONE kind, the first in the order above with users, unioned over its same-named members.

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": {
      "sessionId": "<sessionId>",
      "symbol": "<symbol>"
    },
    "name": "find_usages"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesThe exact (case-sensitive) type, method, property, field, event, enum-member or operator (metadata) name - the qualified Type.Member form for a member - or 'Type.Type' for a type's CONSTRUCTOR (see the tool description: the answer is the type's construction/injection sites, overloads unioned).
sessionIdYesThe session_id returned by analyze_solution. Also takes an absolute .sln/.slnx/.slnf path, analyzed on first use.
includeTestsNoInclude users declared in test projects (default true). false lists production users only, BEFORE the 100-item cap, and 'testUsersFiltered' says how many were left out; viaContract keeps counting every caller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.46516
    • addedInput schema / properties / includeTests
      Added value: +{
      +  "default": true,
      +  "description": "Include users declared in test projects (default true). false lists production users only, BEFORE the 100-item cap, and 'testUsersFiltered' says how many were left out; viaContract keeps counting every caller.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv0.5.46514
    • changedInput schema / properties / symbol / description
      Previous value: -"The exact (case-sensitive) type, method, property, field, event or enum-member name - the qualified Type.Member form for a member - or 'Type.Type' for a type's CONSTRUCTOR (see the tool description: the answer is the type's construction/injection sites, overloads unioned)."New value: +"The exact (case-sensitive) type, method, property, field, event, enum-member or operator (metadata) name - the qualified Type.Member form for a member - or 'Type.Type' for a type's CONSTRUCTOR (see the tool description: the answer is the type's construction/injection sites, overloads unioned)."
  3. Changed1 schema field changedv0.5.46513
    • changedInput schema / properties / sessionId / description
      Previous value: -"The session_id returned by analyze_solution."New value: +"The session_id returned by analyze_solution. Also takes an absolute .sln/.slnx/.slnf path, analyzed on first use."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description goes well beyond them: a 100-item cap on usedBy, kind-dependent result semantics, what an empty usedBy really means (entry points, DI, reflection, source generators leave no reference), and what 'not_found' does and does not imply. This is substantial behavioral context an agent cannot get from annotations; it loses a point mainly for density rather than for missing content.

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

Conciseness3/5

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

The purpose-and-alternatives routing is front-loaded correctly, but the body is a single ~300-word block of semicolon-chained clauses that is hard to scan and mixes result-format documentation into prose. Nearly every clause carries information, but the structure works against quick retrieval.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description fully compensates: it documents the return envelope (symbol, resolvedKind, usedBy with items/count/totalFound/truncated, max 100), the per-item shape ({name, file, line}) including that line is the declaration and file is solution-relative, and the conditional qualifier members (note, namesakes, collision, viaContract, selfReferences, nearest). An agent can call this correctly and interpret the result without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning on top: the bare-name form resolves to ONE kind, the first in the listed order that has users, unioned across same-named members; the 'Type.Type' constructor form returns construction/injection sites. These rules go beyond the schema's own parameter text.

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 opening sentence gives a specific verb and resource ('List who uses a symbol') plus a scoping qualifier ('direct fan-in'), and immediately names the two siblings it is not: impact_of_change (closure/risk) and calls_external (external members). An agent can distinguish it from every other sibling without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('before changing or deleting a symbol, not grep') coupled with named alternatives and the condition that selects each: impact_of_change for transitive closure, calls_external for external members, find_resource_usages for markup keys. It also warns the agent when a result should NOT be trusted as proof of dead code.

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