Skip to main content
Glama
Sign In
gograph

gograph

by ozgurcd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

gograph_strings

Read-onlyIdempotent

Search Go string literals for case-insensitive substrings with OR semantics, returning file, line, literal, and enclosing function; route-shaped terms match path-parameter spellings.

Instructions

Search Go string literals in the indexed source files for one or more case-insensitive substrings (OR semantics), returning file, line, the literal, and its enclosing function. Route-shaped terms match any path-parameter spelling (:id, {id}, *id). Source is read through the confined repository reader; unreadable files are named in a warning. The MCP server refreshes source analysis before the call. Read-only; no side effects. WHEN TO USE: To find raw route strings, URLs, SQL fragments, header names, or messages that are not symbols, instead of grep. NOT TO USE: For symbols (use gograph_query) or registered routes with handlers (use gograph_routes). RETURNS: gograph.results.v1 rows of kind string with total/returned/truncated/next_cursor.

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute path of the checkout you are working in (your cwd or git worktree). Must be this server's repository or one of its git worktrees; the answer then comes from that checkout's own graph. A path elsewhere is refused. Alias: cwd. Omit only when the configured checkout is the one you mean.
termNoSubstring to find inside string literals (e.g. '/api/setup/license')
limitNoMaximum rows per page; the byte budget may return fewer.
queryNoAlias of term
termsNoOptional list of substrings combined with OR semantics
cursorNoOpaque next_cursor for the same graph snapshot and result selection.
no_testsNoExclude *_test.go files
intentionNoTechnical rationale, required for analytical calls selecting an active session.
session_idNoCaller selector returned by session_create. Omission means an independent caller; never inherits server environment or another caller's session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.18

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds real behavior beyond them: the confined repository reader, unreadable files surfaced as warnings, and a source-analysis refresh before the call. It also discloses matching semantics (case-insensitive, multi-term OR, path-parameter spellings ':id', '{id}', '*id') that the agent cannot infer from annotations.

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?

Front-loaded with the action, then behavior, then labeled WHEN TO USE / NOT TO USE / RETURNS sections. Every clause carries information; nothing is redundant filler despite the length.

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

Completeness5/5

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

Nine parameters are all covered by schema descriptions, and although there is no output schema, the description supplies the row shape and pagination envelope (total/returned/truncated/next_cursor). A complex search tool with no required parameters is fully specified for correct invocation.

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 the schema itself documents term, terms, limit, cursor, no_tests, root, intention, and session_id. The description adds only the OR-combination semantics for multiple substrings and confirms pagination fields, so it contributes marginally beyond the schema – baseline territory.

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?

States a specific verb and resource ("Search Go string literals in the indexed source files") plus the exact fields returned (file, line, literal, enclosing function). It explicitly names what it is not ("not symbols" -> gograph_query, registered routes with handlers -> gograph_routes), which separates it from the many gograph_* siblings.

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

Usage Guidelines5/5

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

Has explicit WHEN TO USE (raw route strings, URLs, SQL fragments, header names, messages) with "instead of grep", and an explicit NOT TO USE clause routing to gograph_query and gograph_routes. The alternative selection condition is unambiguous.

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