Skip to main content
Glama
voxmenthe

Search Tools MCP Server

by voxmenthe

get_symbol_usages

Locate all usages of a specified symbol in a repository, applying optional filters by symbol type and file path substrings to narrow results.

Instructions

Run kit usages <repo> <symbol_name> and optionally filter by symbol type at the CLI level and then post-filter the rows by file inclusion/exclusion substrings.

Parameters

repo : str | Path Path or name passed to kit usages. Use full absolute path. symbol_name_or_substring : str The symbol whose usages we want to inspect, or a substring of the symbol name (which can be used to find multiple symbols which share a naming convention). working_directory : str Directory from which to run the command (absolute path). symbol_type : str | None "function" or "method" or "class" file_must_contain : str | None post-filter: Keep only rows whose File column contains this substring. None ⇒ no inclusion filter. file_must_not_contain : str | None post-filter: Discard rows whose File column contains this substring. None ⇒ no exclusion filter.

Returns

list[str] | str Filtered output, ready to print() or write to a file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYes
symbol_typeNo
file_must_containNo
working_directoryYes
file_must_not_containNo
symbol_name_or_substringYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the command execution and post-filtering behavior, plus requirements like absolute paths. However, it does not discuss error conditions, whether the operation is read-only, or the exact format of returned rows, leaving some ambiguity.

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 a single clear sentence followed by a structured parameter list and returns section. Every element serves a purpose; no redundant or promotional content.

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

Completeness4/5

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

For a tool with 6 parameters and no output schema, the description covers all parameters and the return type. It lacks explicit usage examples or error handling, but the operational details are sufficient for an agent to invoke the tool correctly. It could be slightly richer on edge cases, but overall it is well-rounded.

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

Parameters5/5

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

The schema has zero property descriptions, but the description compensates thoroughly: it explains repo path expectations, the substring flexibility for symbol_name, allowed symbol_type values, and the exact post-filter semantics for file_must_contain and file_must_not_contain. This goes far beyond the schema titles.

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 description clearly states that the tool runs `kit usages <repo> <symbol_name>` and applies filters, which is a specific verb+resource for inspecting symbol usages. This distinguishes it from sibling search tools by emphasizing usage inspection with optional type and file filtering.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus sibling tools like smart_code_search or get_repo_symbols. It is purely operational, with no mention of alternatives, prerequisites, or exclusive use cases.

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/voxmenthe/search-tools-mcp'

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