Skip to main content
Glama
Sign In
code-explorer

code-explorer

by vmikhailov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

search_identifiers

Search code identifiers, routes, tables, topics, and endpoints with hybrid vector and trigram matching to find exact or fuzzy matches, optionally filtered by node kind.

Instructions

Fast hybrid vector and trigram search across code identifiers, routes, tables, and topics. Finds exact or fuzzy matches with sub-millisecond ranking.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOptional filter by node kind ('Type', 'Function', 'Member', 'Endpoint', 'Table', 'Topic', 'Project').
limitNoMaximum results to return (default: 15).
queryYesSearch query (symbol name, route, or colloquial keyword).
workspacePathNoOptional workspace root path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.80.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two real behavioral traits: results are ranked by a hybrid of vector and trigram similarity, and relevance ordering is computed cheaply. It does not say whether the operation is read-only, how results are scoped without a workspacePath, or what a result record contains.

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 tight sentences with the capability front-loaded and the matching behavior second. 'Sub-millisecond ranking' borders on marketing flourish but does convey that results come back ordered by relevance rather than raw insertion order.

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?

For a four-parameter read tool with full schema coverage and no output schema, the description covers the core mechanics but leaves two agent-relevant questions open: when to prefer this over a sibling symbol lookup, and what the result shape or scoping default is when workspacePath is omitted.

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 100%, so all four parameters are already documented, and the baseline of 3 applies. The description adds the useful mapping that the searchable surface includes identifiers, routes, tables, and topics, which corresponds to the kind filter's enum values, but adds no format or syntax detail beyond the schema.

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?

States a specific verb ('search') and enumerates the resource surface it covers: code identifiers, routes, tables, and topics. Also names the retrieval mechanism (hybrid vector + trigram) and match modes (exact or fuzzy), which helps distinguish it from a plain symbol lookup. It stops short of naming a sibling it is not, so differentiation is inferred rather than stated.

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?

No explicit when-to-use or when-not guidance. The phrase 'exact or fuzzy matches' hints at the case where precision is unknown, but nothing tells the agent how this differs from find_symbol or get_file_outline, and no prerequisites or exclusions are given.

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

Deploy Server

Other Tools