Skip to main content
Glama

maid_snapshot

Analyze source files to extract public artifacts and generate a manifest snapshot, documenting current APIs and state for onboarding or refactoring.

Instructions

Generate a manifest snapshot from existing code using MAID Runner.

When to use:

  • Onboarding existing code: Create manifests for pre-existing files

  • Before refactoring: Capture current state as a baseline

  • Documentation: Generate manifest to document existing APIs

Key behavior:

  • Analyzes source file to extract public artifacts (functions, classes)

  • Creates a manifest with expectedArtifacts matching current code

  • Optionally generates test stub file for the manifest

Tips:

  • Use before making changes to existing code without manifests

  • The generated manifest serves as a "snapshot" of current state

  • Review and adjust the generated manifest as needed

Args: file_path: Path to the source file to generate a snapshot for output_dir: Directory to output the manifest (default: "manifests") force: Whether to overwrite existing manifest files skip_test_stub: Whether to skip generating test stub file

Returns: SnapshotResult with generation outcome

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
output_dirNomanifests
forceNo
skip_test_stubNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNo
manifest_pathNo
test_stub_pathNo
superseded_manifestsNo
errorsNo
Behavior5/5

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

Since no annotations are provided, the description carries full burden. It details key behaviors: analyzing source files, extracting artifacts, creating manifests, and optionally generating test stubs. This fully discloses the tool's actions.

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?

The description is well-structured with sections, bullet points, and a clear 'Args' list. Every sentence adds value, and the length is appropriate for the tool's complexity.

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 output schema exists, return values are briefly covered. The description covers usage, behavior, and parameters comprehensively. Minor omission: no mention of prerequisites (e.g., MAID Runner installation) or error handling, but overall complete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates fully by listing each parameter (file_path, output_dir, force, skip_test_stub) with clear explanations of their purpose and defaults. This adds significant meaning beyond the raw schema.

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 generates a manifest snapshot from existing code using MAID Runner. It specifies the resource (manifest snapshot) and action (generate), and differentiates from siblings like maid_snapshot_system by focusing on per-file snapshots.

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?

Provides an explicit 'When to use' section with three concrete scenarios (onboarding, refactoring, documentation) and 'Tips' with actionable advice. This gives clear guidance on when to invoke this tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mamertofabian/maid-runner-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server