AppDeploy

Search snapshot file contents

src_grep

Read-onlyIdempotent

Use this when you need to search for patterns in an app's source code. Returns matching lines with optional context. Supports regex patterns, glob filters, and multiple output modes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`glob`	No	Glob pattern to filter files (e.g., '*.ts')
`path`	No	Directory path to search within
`app_id`	Yes	Target app id
`context`	No	Lines before and after (overrides before/after_context)
`pattern`	Yes	Regex pattern to search for (max 500 chars)
`version`	No	Version to search (defaults to applied version)
`output_mode`	No	content=matching lines, files_with_matches=file paths only, count=match count per file	content
`line_numbers`	No	Include line numbers in output
`after_context`	No	Lines to show after each match (0-20)
`max_file_size`	No	Max file size to scan in bytes (default 10MB)
`before_context`	No	Lines to show before each match (0-20)
`case_insensitive`	No	Enable case-insensitive matching
`continuation_token`	No	Token from previous response for pagination

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare this as a safe read-only operation, so the burden is lowered. The description adds that it returns matching lines with optional context, plus mentions output modes, which is useful behavioral information. However, it does not disclose pagination, size limits, or default version behavior beyond what schema annotations provide.

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?

Two sentences, front-loaded with a direct 'Use this when' hook. Every sentence earns its place, with no fluff or redundancy.

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?

The tool has 13 parameters and no output schema, but the description provides a solid overview of purpose, typical use, and key capabilities. It doesn't mention pagination or version defaults, but those are well-covered by the schema, and the description adequately addresses the core search functionality.

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 coverage is 100%, so the description need not repeat parameter details. It mentions regex, glob filters, and output modes, which map to existing schema descriptions, but adds no new semantic depth beyond what the schema already provides.

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 tool searches for patterns in app source code, with a specific verb and resource. It differentiates from sibling tools like src_read and src_glob by mentioning regex, glob filters, and output modes.

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

Usage Guidelines4/5

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

It provides explicit context for when to use the tool ('when you need to search for patterns'), but does not explicitly mention when not to use it or name alternative tools. The feature list helps distinguish it from siblings, making the guidance clear but not exhaustive.

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

All AppDeploy tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation4/5

Most tools have distinct purposes, but the 5 secrets-related tools (create_secret_entry, delete_app_secrets, get_secret_entry_status, list_app_secrets, set_app_secrets) are numerous and could cause confusion. Similarly, deploy_app and apply_app_version both involve deployment but with different contexts. Overall, descriptions help differentiate, but some overlap remains.

Naming Consistency4/5

The majority of tools follow verb_noun pattern (e.g., deploy_app, get_apps). However, the src_ prefix tools (src_glob, src_grep, src_read) deviate by using a noun prefix instead of a verb, creating a slight inconsistency. Otherwise, naming is clear and predictable.

Tool Count5/5

With 21 tools, the server covers deployment, domain management, secrets, source inspection, and asset upload without being overly large. The count is well-scoped for a deployment platform, each tool serving a necessary role.

Completeness4/5

Core workflows (deploy, status, secrets, source inspection) are well-covered. However, there are minor gaps: no tool to list available templates or manage app metadata beyond deployment. The surface is mostly complete but could benefit from a few additional administrative tools.

Resources

Need Help?