Skip to main content
Glama

write_setup_doc

Create a setup or deployment document with prerequisites, steps, and verification. The document is indexed and auto-pushed to git for infrastructure and CI/CD guides.

Instructions

Create a setup, deployment, or infrastructure document, index it, and auto-push.

    Side effects: creates setup/{slug}.md in the docs path, indexes it
    into the vector store, and pushes to git if configured. Overwrites
    an existing file with the same title.

    Use for environment setup guides, CI/CD configuration, Docker or
    infrastructure docs, and deployment runbooks.
    Use write_architecture_doc() for system design rather than how-to guides.

    Args:
        title: Short title (e.g. "Local Development Setup")
        prerequisites: Tools, accounts, or config required before starting
        steps: Step-by-step instructions (numbered list recommended)
        verification: How to confirm the setup is working correctly
        troubleshooting: Common issues and their fixes (optional)
        project: Target project name (optional)

    Returns:
        Saved filename, chunk count, and whether auto-push succeeded.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsYes
titleYes
projectNo
verificationYes
prerequisitesYes
troubleshootingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description details side effects (creates file, indexes, auto-push) and overwrites existing files. It mentions return values but lacks specifics on permissions or failure modes, which is a minor gap.

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 well-structured with headers for side effects, usage, args, and returns. It is slightly long but every sentence adds value; could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters, side effects, return value, and sibling tools, the description covers all essential aspects: purpose, usage, parameter meanings, return format, and relationship to alternatives.

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?

Despite 0% schema description coverage, the description provides an Args section explaining all six parameters (title, prerequisites, steps, verification, troubleshooting, project) with clear roles and format suggestions.

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 creates a setup, deployment, or infrastructure document, with specific verbs and resource (create, index, auto-push). It distinguishes from sibling write_architecture_doc by naming it directly.

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?

Explicitly lists use cases (environment setup, CI/CD, Docker, deployment runbooks) and directs to use write_architecture_doc for system design, providing clear when-to-use and when-not-to-use guidance.

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/dl4rce/flaiwheel'

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