Skip to main content
Glama

search_symbols

Search code symbols across repositories with filters for name, type, language, complexity, and documentation. Locate functions, classes, and other elements precisely without reading entire files.

Instructions

Search for symbols across the repo with flexible filters.

All parameters optional — combine for powerful filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoexact match on type (function, class, method, struct, etc.)
queryNocase-insensitive substring match on symbol name
formatNo"full" (default) or "compact" (abbreviated)full
parentNocase-insensitive substring match on parent class name
has_docNoTrue = only symbols with doc, False = only without
languageNofilter by file extension without dot (e.g., "py", "js", "go")
min_complexityNominimum cyclomatic complexity

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as performance, pagination, or read-only nature. It adds minimal value beyond the input schema.

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?

The description is very concise with two sentences, front-loading the purpose. Every word serves a purpose, making it efficient and easy to parse.

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

Completeness2/5

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

Given 7 optional parameters and no annotations, the description is too minimal. It does not explain search behavior, result ordering, or limitations, leaving the agent with incomplete context despite an output schema.

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 100%, so the baseline is 3. The description adds that parameters can be combined for powerful filtering, which provides some context but does not significantly enhance parameter understanding.

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?

The description clearly states the tool searches for symbols with flexible filters. However, it does not differentiate from sibling tools like get_symbol, get_symbols, or search_graph, which could also search symbols.

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

Usage Guidelines3/5

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

It mentions all parameters are optional and can be combined, implying flexible usage, but does not provide when-to-use or when-not-to-use guidance relative to alternatives.

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/ThinkyMiner/codeTree'

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