Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

autopilot

Generate a CLAUDE.md / copilot-instructions.md that makes any AI self-managing forever. Writes a configuration file to disk — will overwrite an existing file at the target path. No auth required beyond a valid instance_id. The generated file instructs Claude, Cursor, Copilot, Windsurf, or Gemini to automatically call session_start at window open, learn_from_attempts after every fix, and session_end before closing — without being asked. Returns the generated file content as a string and the path where it was written. Use style="minimal" for just the three hooks; style="full" for the complete ruleset with examples. One command. Every AI. Always on. Use setup_ai_memory instead if you want an interactive one-shot setup that also creates an instance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNominimal = just the hooks, full = full ruleset with examples (default: full)
editorNoTarget editor (default: claude)
instance_idNoUUID of the cache instance.
project_nameNoYour project name (used in generated instructions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the tool writes to disk, that it will overwrite an existing file at the target path, that no auth is needed beyond a valid instance_id, and what is returned (content string plus written path). It stops short of saying how the target path is derived or whether directories are created.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core facts are front-loaded and useful, but the marketing tagline 'One command. Every AI. Always on.' is pure filler, and the editor list is repeated from the enum. Trimming those would make it tighter without losing information.

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?

For a file-writing tool with no output schema, the description covers the important ground: mutation risk (overwrite), auth requirement, return values, and style variants. The main gap is where the file lands by default, which matters for a tool that writes to disk.

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 description coverage is 100%, so the baseline is 3. The description restates the style semantics already in the schema and mentions instance_id as the auth requirement, but adds no new meaning for editor or project_name beyond what the schema documents.

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?

States a specific verb and artifact: generate a CLAUDE.md / copilot-instructions.md configuration file. It also names the sibling it is not (setup_ai_memory) and the condition that selects that sibling, so an agent can distinguish the two without opening either schema.

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 routes the agent: use this for a one-command file generation, use setup_ai_memory instead for an interactive one-shot setup that also creates an instance. It also gives selection guidance between style values (minimal = three hooks, full = complete ruleset).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.