Skip to main content
Glama
Sign In

AppDeploy

by ai.appdeploy
OverviewDiscussionsAdmin

Read snapshot file

src_read
Read-onlyIdempotent

Use this tool to read a stored source file by app_id and path (file_path is also accepted). Optionally set version, zero-based line offset and limit. Omitted version reads the latest attempted snapshot. MCP version 2.12.

Input Schema

NameRequiredDescriptionDefault
pathNoPath to the file to read. Required unless file_path is supplied.
limitNoNumber of lines to return (max 2000)
app_idYesTarget app id
offsetNoLine offset to start reading from (0-indexed)
versionNoVersion to read from. Omit to use the latest stored snapshot (last_attempt_version).
file_pathNoCompatibility alias for path. Prefer path; if both are supplied they must match.
mcp_versionNoSet to "2.12", the MCP version in this tool's description. Use this tool's version, not another tool's version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mcp_version / description
      Previous value: -"Set to \"2.11.7\", the MCP version in this tool's description. Use this tool's version, not another tool's version."New value: +"Set to \"2.12\", the MCP version in this tool's description. Use this tool's version, not another tool's version."
  2. Changed1 schema field changed
    • changedInput schema / properties / mcp_version / description
      Previous value: -"Set to \"2.11.0\", the MCP version in this tool's description. Use this tool's version, not another tool's version."New value: +"Set to \"2.11.7\", the MCP version in this tool's description. Use this tool's version, not another tool's version."
  3. Changed5 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "path"
+    ]
+  },
+  {
+    "required": [
+      "file_path"
+    ]
+  }
+]
    • changedInput schema / properties / file_path / description
      Previous value: -"Path to the file to read"New value: +"Compatibility alias for path. Prefer path; if both are supplied they must match."
    • addedInput schema / properties / mcp_version
      Added value: +{
+  "description": "Set to \"2.11.0\", the MCP version in this tool's description. Use this tool's version, not another tool's version.",
+  "maxLength": 32,
+  "minLength": 1,
+  "pattern": "^\\d+\\.\\d+(?:\\.\\d+)?$",
+  "type": "string"
+}
    • addedInput schema / properties / path
      Added value: +{
+  "description": "Path to the file to read. Required unless file_path is supplied.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "app_id",
-  "file_path"
-]New value: +[
+  "app_id"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / version / description
      Previous value: -"Version to read from (defaults to applied version)"New value: +"Version to read from. Omit to use the latest stored snapshot (last_attempt_version)."
  5. Changed1 schema field changed
    • changedInput schema / properties / version / description
      Previous value: -"Version to read from. Omit to use the latest stored snapshot (last_attempt_version)."New value: +"Version to read from (defaults to applied version)"
  6. Changed1 schema field changed
    • changedInput schema / properties / version / description
      Previous value: -"Version to read from (defaults to applied version)"New value: +"Version to read from. Omit to use the latest stored snapshot (last_attempt_version)."
  7. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds meaningful context beyond them: the default-to-latest-snapshot semantics for omitted version and the alias resolution rule for file_path. No return format is described, but that is minor for a read tool.

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 compact sentences, front-loaded with the core action and required identifiers. Every sentence carries information; the trailing 'MCP version 2.12' is slightly awkward but ties to the mcp_version parameter.

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?

A read-only tool with full schema coverage and no output schema; the description covers the essential calling semantics including version defaulting and the path alias. Only missing piece is any hint about the shape of returned content.

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 all seven parameters are already documented. The description restates the offset/limit and version defaults and notes the file_path alias, but adds little beyond the schema's own descriptions.

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: 'read a stored source file by app_id and path'. Clear what it does, though it does not explicitly distinguish itself from siblings like src_glob or src_grep for file discovery/search.

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?

Explains the optional version/offset/limit behavior and that omitting version reads the latest attempted snapshot. However, it gives no explicit when-to-use guidance versus src_glob or src_grep, leaving routing to inference.

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

All AppDeploy toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources