Skip to main content
Glama
cacheout-app

cacheout-mcp

Official
by cacheout-app

cacheout_configure_autopilot

Idempotent

Configures autopilot policy for the headless daemon by validating and atomically writing configuration.

Instructions

Configure the autopilot policy for the headless daemon.

Uses a validate-then-write flow:

  1. Writes candidate config to autopilot.candidate.json (0600)

  2. If daemon running: validates via socket; else validates locally

  3. Invalid: deletes candidate, returns errors

  4. Valid: atomically renames candidate to autopilot.json

  5. If daemon: sends SIGHUP and polls for config generation increment

The local validator mirrors the daemon's shared validator exactly:

  • version must be 1

  • enabled must be boolean

  • Rules: actions must be 'pressure-trigger' or 'reduce-transparency'

  • Webhook (if present): url required, format = 'generic', timeout_s 1-60

  • Telegram (if present): bot_token + chat_id required, timeout_s 1-60

Args: params: Config object to validate and apply.

Returns: str: JSON with success status, validation errors, and any warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description details the entire validate-then-write flow, including file writes, validation via socket or locally, atomic rename, SIGHUP, and polling. This goes well beyond the annotations which only hint at idempotency and non-destructiveness.

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: purpose first, then numbered steps, then validation rules. It is slightly verbose but every part adds value.

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 the tool's moderate complexity, the description covers the config structure, validation details, execution flow, and return format. No gaps remain.

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 schema description coverage at 0%, the description fully compensates by specifying validation rules for version, enabled, rules, webhook, and telegram, including exact required fields and value ranges.

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 'Configure the autopilot policy for the headless daemon', which is a specific verb-resource combination. It distinguishes from siblings which deal with alerts, cache, health, etc.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. There are 11 sibling tools, but no mention of when to choose this one over them.

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/cacheout-app/cacheout-mcp'

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