Skip to main content
Glama

search_graph

Read-onlyIdempotent

Find code symbols using keyword, regex, or semantic queries, with results showing files, lines, and dependency 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
labelNo
limitNo
queryNo
detailNodefault
fieldsNo
formatNotree
offsetNo
projectYes
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. 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."
  2. Changed1 schema field changedv0.10.4
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "type": "object"
      -}New value: +null
  3. 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."
  4. Changed1 schema field changedv0.9.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  5. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish read-only/idempotent/non-destructive behavior. The description adds useful context about result rows and relationship edge kinds, but it does not disclose behavioral details such as how filters combine, how degree limits affect traversal, or what output formats contain. With annotations covering safety, this is adequate but not rich.

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 compact sentences with no filler; the main verb and resource appear immediately. The jargon density is high, but every clause adds information, making it appropriately sized for a first-level description.

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 20-parameter search tool with no output schema, this description is too thin. It gives the result row shape but not enough guidance on filter semantics, output formatting, pagination, or the meaning of many parameters, leaving the agent to infer critical calling details.

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 5% across 20 parameters, so the description must compensate. It explains the core query modes and regex filters, but leaves most parameters—detail, fields, format, offset, degree bounds, include_connected, exclude_entry_points—unexplained. This is a significant gap.

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 identifies a symbol search tool with specific query modes (BM25, regex filters, semantic_query) and describes what rows contain. It does not explicitly distinguish this from siblings like search_code or query_graph, so it loses the top score.

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 description implies usage for symbol lookup across relationship types, but never states when to prefer this tool over search_code or query_graph, or when not to use it. There is no explicit alternative routing or exclusion guidance.

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