Skip to main content
Glama

grep_app_search

Search public code by literal string or regex, with optional language and repo filters, and return matched file paths, line numbers, and code snippets.

Instructions

Search public code on grep.app (keyless; browser fallback for bot checks).

Accepts a literal string or regex, optional language and repository filters. Returns repo, path, matched line numbers and a cleaned code snippet.

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": "grep_app_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNo
limitNo
queryYes
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does add useful context: no API key required, and a browser fallback path exists when bot checks trigger. It does not mention rate limits, result caps, or failure modes beyond that, but the auth and fallback disclosure is meaningful value beyond what structured fields provide.

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?

Three short sentences, each front-loaded with the key information: purpose, accepted input, and return shape. No filler, though the parenthetical about browser fallback breaks the flow slightly between the core purpose and input details.

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?

The description covers the return shape (repo, path, line numbers, snippet), which matters since no output schema exists. Gaps remain: the 'limit' parameter is unexplained, and there is no note on result caps or how the browser fallback affects latency or reliability for a four-parameter tool.

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 0% across four parameters, so the description must compensate; it explains that query accepts a literal string or regex and that language and repository filters exist, which maps meaning onto three of the four params. The 'limit' parameter is never mentioned, leaving result-count behavior undocumented in both schema and description.

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 and resource: 'Search public code on grep.app', which is concrete and immediately distinguishes it from a generic web_search. It does not explicitly name or contrast with the closest sibling, github_search, so the differentiation is implicit in naming the source service.

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 'keyless' note and 'browser fallback for bot checks' hint at operational context, and 'literal string or regex' implies when the tool fits (code-pattern lookups). However there is no explicit when-to-use vs when-not-to-use guidance or a named alternative such as github_search for repository-hosted code.

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