Skip to main content
Glama

search_graph

Read-onlyIdempotent

Find code symbols in a project knowledge graph using BM25 text, regex name/qualified-name/file filters, or semantic queries, with call, usage, inheritance, and implementation relationships.

Instructions

Find symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoResource kind, e.g. Deployment.
labelNo
limitNo
queryNo
detailNodefault
fieldsNo
formatNotree
offsetNo
projectYes
namespaceNoResource namespace.
max_degreeNo
min_degreeNo
qn_patternNo
file_patternNo
name_patternNo
relationshipNo
semantic_limitNo
semantic_queryNoNot with query.
semantic_offsetNo
include_connectedNo
max_output_tokensNo
exclude_entry_pointsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.1
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "Resource kind, e.g. Deployment.",
      +  "type": "string"
      +}
    • addedInput schema / properties / namespace
      Added value: +{
      +  "description": "Resource namespace.",
      +  "type": "string"
      +}
  2. Changed14 schema fields changedv0.11.0
    • removedInput schema / properties / detail / description
      Removed value: -"ids: bare qualified-name enumeration (one column) — cheapest form for wide sweeps where per-row metadata is noise. default: full rows."
    • removedInput schema / properties / fields / description
      Removed value: -"Extra per-node property columns, e.g. complexity, cognitive, signature, docstring, return_type, is_test, lines(int). Core row columns (qn/label/file/lines/in/out) are always present — do not request them here. Missing values emit as empty cells."
    • removedInput schema / properties / format / description
      Removed value: -"Response encoding. tree (default): prefix-grouped text rows. json: the SAME tree model as structured JSON (groups + column-ordered row arrays)."
    • addedInput schema / properties / limit / default
      Added value: +50
    • removedInput schema / properties / limit / description
      Removed value: -"Max results per call. Default 50. Response carries 'total' (full match count) and 'has_more' (true if truncated) so callers can detect the limit and paginate."
    • addedInput schema / properties / limit / maximum
      Added value: +500
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / max_output_tokens
      Added value: +{
      +  "default": 3200,
      +  "maximum": 1000000,
      +  "minimum": 128,
      +  "type": "integer"
      +}
    • removedInput schema / properties / offset / description
      Removed value: -"Skip the first N matching nodes. Combine with 'limit' to page: increment offset by limit and re-call while has_more is true."
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • removedInput schema / properties / query / description
      Removed value: -"Natural-language or keyword full-text search using BM25 ranking. Tokens are split on whitespace; camelCase identifiers are indexed as individual words (updateCloudClient → update, cloud, client). Results are ranked with structural boosting: Functions/Methods +10, Routes +8, Classes/Interfaces +5. Noise labels (File/Folder/Module/Variable) are filtered out. When provided, name_pattern is ignored."
    • addedInput schema / properties / semantic_limit
      Added value: +{
      +  "default": 50,
      +  "maximum": 500,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / semantic_offset
      Added value: +{
      +  "default": 0,
      +  "maximum": 99998,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / semantic_query / description
      Previous value: -"MUST be an ARRAY of keyword strings (e.g. [\"send\",\"pubsub\",\"publish\"]) — NOT a single string. Each keyword is scored independently via per-keyword min-cosine; results reflect functions that score well on ALL keywords. Requires moderate/full index mode. Results appear in the 'semantic_results' field (separate from 'results')."New value: +"Not with query."
  3. Changed1 schema field changedv0.10.4
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "type": "object"
      -}New value: +null
  4. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "default",
      +  "description": "ids: bare qualified-name enumeration (one column) — cheapest form for wide sweeps where per-row metadata is noise. default: full rows.",
      +  "enum": [
      +    "ids",
      +    "default"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Extra per-node property columns, e.g. complexity, cognitive, signature, docstring, return_type, is_test, lines(int). Core row columns (qn/label/file/lines/in/out) are always present — do not request them here. Missing values emit as empty cells.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / format
      Added value: +{
      +  "default": "tree",
      +  "description": "Response encoding. tree (default): prefix-grouped text rows. json: the SAME tree model as structured JSON (groups + column-ordered row arrays).",
      +  "enum": [
      +    "tree",
      +    "json"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Max results per call. Default 200. Response carries 'total' (full match count) and 'has_more' (true if truncated) so callers can detect the limit and paginate."New value: +"Max results per call. Default 50. Response carries 'total' (full match count) and 'has_more' (true if truncated) so callers can detect the limit and paginate."
  5. Changed1 schema field changedv0.9.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  6. First observedv1.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare the safe read-only/idempotent/closed-world profile, so the description's remaining job is to add context. It does so by disclosing the output row shape (qn/file/lines plus in/out edges) and the relationship types traversed (CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS), which annotations cannot convey. It omits pagination/limit and error behavior, keeping it from a 5.

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 dense sentences with no filler and the primary retrieval modes front-loaded. Jargon abbreviations ('qn', 'in/out') slightly reduce readability, but there is no wasted text.

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?

For a 22-parameter tool with no output schema and near-zero schema description coverage, the description is far too thin: most filters are undocumented and the return contract is only sketched. It should explain the filter surface (patterns, degrees, relationship, detail/format) and pagination for an agent to call it correctly.

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

Parameters2/5

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

Schema description coverage is only 14% across 22 parameters, so the description must carry the burden and largely does not. It gives meaning to a handful (query, name_pattern/qn_pattern, semantic_query) but leaves kind, label, limit, offset, format, detail, degree bounds, relationship, include_connected, max_output_tokens and more entirely unexplained in both schema and prose.

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+resource ('Find symbols') and enumerates three distinct retrieval modes (BM25 query, regex name/qn filters, semantic_query), so an agent knows it searches the symbol graph. It does not differentiate itself from siblings like query_graph or search_code, so it stops short of a 5.

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?

The three modes imply how to invoke it (text vs regex vs semantic), giving indirect guidance on routing between retrieval strategies. However, it never states when to prefer search_graph over query_graph, search_code or trace_path, nor any prerequisites or exclusions.

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