Skip to main content
Glama
Sign In
Naveen Ayalla

Naveen Ayalla

by naveenayalla1-CS50
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_code

Search for keywords or patterns across the codebase and retrieve file path, line number, and surrounding context.

Instructions

Search for a keyword or pattern across the codebase. Returns file path, line number, and surrounding context.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword, function name, or pattern to search for
filePatternNoGlob pattern to limit search, e.g. "**/*.ts"
maxResultsNoMax results to return (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
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 basic behavior (search, return results), but lacks details such as case sensitivity, regex support, or permission requirements. The description is adequate but not exhaustive.

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?

The description is concise, consisting of two sentences with no wasted words. It front-loads the purpose and immediately states the return format. Slight improvement could be made by integrating usage guidance.

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?

Given the lack of output schema, the description appropriately states what is returned. The parameters are fully described in the schema. The sibling tools provide context. Completeness is high for a search tool with moderate complexity.

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 each parameter is already described. The tool description adds minimal extra meaning beyond 'keyword or pattern'. Baseline 3 is appropriate as no additional context is provided.

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 the action ('Search for a keyword or pattern'), the resource ('codebase'), and what is returned ('file path, line number, and surrounding context'). It is distinct from sibling tools list_files and read_file, which focus on listing and reading files, not searching content.

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?

No explicit guidance on when to use this tool versus alternatives. The context implies it is for finding code occurrences, but there is no mention of when not to use it or alternative strategies.

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