Skip to main content
Glama
theburgerllc

AI Development Pipeline MCP

by theburgerllc

run_augment_prompt

Send prompts to a local Augment coding agent for AI-assisted development tasks within the Claude AI development pipeline.

Instructions

Send a prompt to the local Augment coding agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes

Implementation Reference

  • The handler function for the 'run_augment_prompt' tool. It writes the provided prompt to './augment-prompt.txt' as a demo implementation for sending to a local Augment coding agent, returning success or failure message.
    async ({ prompt }) => {
      // You need to provide a local API endpoint, CLI, or plugin to accept this
      // For demo: write to a file for augment to pick up, or invoke augment via CLI/API
      try {
        fs.writeFileSync('./augment-prompt.txt', prompt, 'utf8');
        return { content: [{ type: 'text', text: 'Prompt sent to Augment.' }] };
      } catch (err: any) {
        return { content: [{ type: 'text', text: 'Failed to send prompt to Augment.' }] };
      }
    }
  • Input schema for the tool, defining a single 'prompt' parameter as a string using Zod.
    { prompt: z.string() },
  • Registration of the 'run_augment_prompt' tool on the MCP server using server.tool(), including name, description, schema, and handler.
    server.tool(
      'run_augment_prompt',
      'Send a prompt to the local Augment coding agent',
      { prompt: z.string() },
      async ({ prompt }) => {
        // You need to provide a local API endpoint, CLI, or plugin to accept this
        // For demo: write to a file for augment to pick up, or invoke augment via CLI/API
        try {
          fs.writeFileSync('./augment-prompt.txt', prompt, 'utf8');
          return { content: [{ type: 'text', text: 'Prompt sent to Augment.' }] };
        } catch (err: any) {
          return { content: [{ type: 'text', text: 'Failed to send prompt to Augment.' }] };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions sending a prompt but doesn't explain what the agent does (e.g., generates code, provides explanations), potential side effects, authentication needs, rate limits, or response format. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity of interacting with a coding agent, no annotations, no output schema, and low schema coverage, the description is incomplete. It fails to address key aspects like what the agent does, response expectations, or error handling, leaving the agent unsure of the tool's full context and behavior.

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?

The description adds minimal meaning beyond the input schema, which has 0% coverage. It implies the 'prompt' parameter is a string sent to the agent, but doesn't specify format, content expectations, or constraints. With low schema coverage, the description doesn't fully compensate, resulting in a baseline score due to the single parameter.

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?

The description clearly states the action ('Send a prompt') and target ('to the local Augment coding agent'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'run_shell_command' or 'run_project_tests' that might also involve execution, leaving room for improvement in distinguishing its unique role.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description lacks context about its intended use cases, prerequisites, or exclusions, such as whether it's for code generation, debugging, or other tasks compared to siblings like 'run_shell_command' or 'run_project_tests'.

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/theburgerllc/ai-development-pipeline-mcp'

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