Skip to main content
Glama

Find a Symbol by Name

find_symbol
Read-onlyIdempotent

Locate C# types, methods, properties, fields, events, enum members, and operators by name substring. Returns ranked matches with kind, signature, and declaring type for symbol lookup.

Instructions

Find types, methods, properties, fields, events, enum members and operators whose name contains the query (case-insensitive). Returns each match with kind ('type'/'method'/'property'/'field'/'event'/'enum_member'/'operator'), name, declaring type (a nested type's outer one; a member of a nested type adds 'outerType'), namespace, a signature, and 'project' where two hits would read alike. Use this to locate a symbol before find_usages / call_graph / get_context - every kind listed here is one find_usages / impact_of_change resolve. Types are listed first, then methods, then properties (handwritten + source-generated - a generated property carries a '// source-generated' note in its signature), then fields, events and enum members (an enum member's signature is its qualified Enum.Member form, the string the fan-in tools take), then user-defined operators + conversions. A user-defined operator is found by its METADATA name (query 'op_Equality' / 'op_Addition' / 'op_Implicit'; 'op_' lists them all). Not indexed, so an empty answer is expected for them: local variables, parameters, labels, namespaces, and C# generated into obj/ that carries real declarations (protobuf/Grpc.Tools, T4, Refit), and a Blazor component written only in a .razor file - a zero-hit answer says which in 'generatedSourcesNote'. Results are ranked by match quality FIRST - exact name, then case-insensitive exact, then prefix, then substring - and only within one rank by the kind order above, so the cap never hides an exact match behind weaker substring hits. Returns a capped envelope (items/count/totalFound/truncated), max 100 - if truncated, the exact/prefix matches are the ones you got; narrow the query (a longer substring) to see the weaker rest. If the query matches nothing, the response carries a 'nearest' suggestion - the closest declared name (a likely typo/case-mismatch); a match never carries one. With no nearest either, a 'note' says a missing name is not a missing feature.

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>",
      "query": "<query>"
    },
    "name": "find_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA substring of the symbol name to search for (type, method, property, field, event, enum member or operator).
sessionIdYesThe session_id returned by analyze_solution. Also takes an absolute .sln/.slnx/.slnf path, analyzed on first use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds substantial behavior: the capped envelope (items/count/totalFound/truncated), the 100-item cap, ranking order and how truncation interacts with it, and the 'nearest' / 'generatedSourcesNote' fallbacks on zero hits. It also discloses operator lookup by metadata name ('op_Equality', 'op_' lists all), which is non-obvious and would otherwise cause failed calls.

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?

Purpose and usage are correctly front-loaded, but the middle is a single run-on enumeration of kind ordering and generated-source caveats that is hard to parse on a first read. The content mostly earns its place, yet the density (nested parentheticals, quoted notes inside sentences) costs readability where a shorter list would convey the same facts.

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, so the description carries the return-value burden and does so: it names the envelope fields, the per-match fields (kind, name, declaring type, namespace, signature, project), and the special cases for nested types, source-generated properties, and enum member signatures. Nothing an agent needs to call it correctly or interpret the result is missing.

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, but the description adds real meaning beyond the schema: the query is a case-insensitive substring, narrowing is done by supplying a longer substring, and operators are queried by metadata name. It does not explain sessionId beyond what the schema already says, which keeps it from a 5.

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?

Opens with a specific verb and resource plus the exact set of symbol kinds covered ('types, methods, properties, fields, events, enum members and operators') and the matching rule (case-insensitive substring). It also states what it is not ('Not indexed... local variables, parameters, labels, namespaces'), which lets an agent separate it from lookup siblings 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 Guidelines4/5

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

Explicitly sequences the tool: 'Use this to locate a symbol before find_usages / call_graph / get_context', and adds that every kind listed is resolvable by find_usages / impact_of_change. That is strong when-to-use guidance, but it never routes the agent away from overlapping siblings such as find_by_attribute, find_by_semantics, or symbol_signature.

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