Skip to main content
Glama

Autopilot settings

autopilot_get
Read-onlyIdempotent

The autopilot settings of each of your characters (or one): on or off, platforms and their weekly schedule (UTC), the brief, the post mix, whether posts wait for approval, and the daily credit cap; plus credits per post format and which platforms are connected. Pass version to autopilot_update to avoid overwriting a change made meanwhile.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
characterIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: the exact data surface returned, the UTC convention for schedules, and an optimistic-concurrency note tying the returned version to autopilot_update. Minor gap: it doesn't say explicitly that version is part of this tool's response, though that is strongly implied.

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?

Front-loaded with the resource, then the field inventory, then the concurrency caveat. The long field list is justified because no output schema exists, so this is the only documentation of return values. Slightly dense, but no filler.

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?

With no output schema, the description correctly spends its space documenting the returned fields, and it covers the one optional parameter's effect. For a simple settings read, the only real omissions are error/empty behavior and confirmation that version appears in the response.

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

Parameters4/5

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

The single characterId parameter has 0% schema description coverage, so the description must carry the meaning — and it does: 'each of your characters (or one)' establishes that the parameter is an optional filter and what omitting it does. It doesn't specify the identifier format, but the intent is clear.

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 names the specific resource (autopilot settings) and enumerates its contents — on/off, platforms and weekly schedule in UTC, brief, post mix, approval wait, daily credit cap, credits per post format, connected platforms. It also states the scope ('each of your characters (or one)'), which separates it from autopilot_list_posts. The verb 'get' is only implicit, but the retrieved object is unmistakable.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: omitting characterId returns all characters, supplying it narrows to one. The second sentence gives a real cross-tool instruction (pass the version to autopilot_update to avoid clobbering concurrent changes), which is useful workflow guidance. However, there is no explicit 'use this when...' framing or exclusion against siblings beyond the field list.

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.

Resources