Skip to main content
Glama
Sign In

Agency Autopilot

by com.jiyumarketing.mcp
OverviewDiscussionsAdmin

Autopilot: record how this agency wants it to work

autopilot_preference

Record how this agency wants its Autopilot to work, in the person's words ("never touch the brand campaign", "write posts in German", "always ask before publishing pages", "don't do that again"), for every client (leave client out) or one. Preferences come first in every Autopilot run and win over data from other clients. Call it whenever the person says how Autopilot should or should not behave. Adds only; autopilot_preference_remove drops one.

Input Schema

NameRequiredDescriptionDefault
textYesThe preference in the person's words, clear and specific
clientNoOne client's name; leave out for every client

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / action
      Removed value: -{
-  "enum": [
-    "add",
-    "list",
-    "remove"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / client / description
      Previous value: -"add: one client's name; leave out for every client"New value: +"One client's name; leave out for every client"
    • removedInput schema / properties / key
      Removed value: -{
-  "description": "remove: the key from list",
-  "type": "string"
-}
    • changedInput schema / properties / text / description
      Previous value: -"add: the preference in the person's words, clear and specific"New value: +"The preference in the person's words, clear and specific"
    • changedInput schema / required
      Previous value: -[
-  "action"
-]New value: +[
+  "text"
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds genuinely non-obvious behavior: preferences take precedence in every run and 'win over data from other clients,' and it confirms additive-only semantics. Return format is unspecified, but the precedence rule is high-value context beyond the annotations.

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 purpose is front-loaded and the removal behavior is appended efficiently. The parenthetical example list is long but each example clarifies the expected input, so it earns its place; overall slightly dense but not wasteful.

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 two-parameter, no-output-schema tool this covers what it does, when to call it, the precedence behavior, and how to undo it. The only gap is not disambiguating from autopilot_note/autopilot_feedback, which is a minor omission given the clear primary purpose.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by showing example phrasings of the required 'text' value and by restating that leaving 'client' out applies the preference to every client, reinforcing the field's semantics.

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 resource (record how this agency wants its Autopilot to work) with concrete illustrative examples of the preference text. It also distinguishes itself from the closest sibling by noting 'Adds only; autopilot_preference_remove drops one.' An agent can tell it apart from autopilot_preferences and autopilot_preference_remove without opening any schema.

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

Usage Guidelines4/5

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

'Call it whenever the person says how Autopilot should or should not behave' gives a clear trigger condition, and the removal alternative is named. It does not, however, distinguish itself from the confusable siblings autopilot_note and autopilot_feedback, so the routing guidance is good but not exhaustive.

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

All Agency Autopilot toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources