Skip to main content
Glama
Sign In

Agency Autopilot

by com.jiyumarketing.mcp
OverviewDiscussionsAdmin

Autopilot: the set-up questions (cards to click)

autopilot_setup_questions
Read-onlyIdempotent

Autopilot's set-up questions, so it works the way this agency does: required before a client is first switched to shadow or on. The agency's part is asked once (what they do for most clients, how hands-on, how they want to hear from it, the client report); each client's part is short (what the agency does for it, what a win is, what's off-limits, low-star review replies, anything else). Each question has its options and default, with any answers already given. Ask them in the chat in one message, or give the person setup_page (a web page of answers to click). Call it as soon as set-up is needed, without asking first. Changes nothing.

Input Schema

NameRequiredDescriptionDefault
clientNoClient name from list_clients; leave out for only the agency's part
agency_questionsNotrue to show the agency's questions again (to change them). Left out, an agency that already answered gets one summary line, not the questions (asked once).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agency_questions
      Added value: +{
+  "description": "true to show the agency's questions again (to change them). Left out, an agency that already answered gets one summary line, not the questions (asked once).",
+  "type": "boolean"
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so 'Changes nothing' merely confirms them. The description adds real context beyond that: answers already given are included, the agency's part is asked once and collapses to a summary line afterwards, and the caller should not pause to ask permission first.

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?

Purpose is front-loaded in the first clause and every sentence carries information. It is long and parenthetical, but the density is functional rather than 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 fills that gap by describing what comes back: each question with its options, default, and any answers already given. Combined with the trigger condition and delivery modes, an agent has what it needs to call it correctly.

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 coverage is 100%, so the schema already carries the meaning of both parameters. The description reinforces the one-time agency behavior behind agency_questions and the scope of client, but adds little syntax or format detail beyond what the schema states — baseline 3.

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's set-up questions — and details exactly what those questions cover (agency part vs per-client part, with options and defaults). It is clearly distinct from a save/answer tool, though it never names a sibling to contrast with, so it falls just short of the top mark.

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?

It gives a concrete trigger ('required before a client is first switched to shadow or on') and an imperative ('Call it as soon as set-up is needed, without asking first'), plus two delivery paths (ask in the chat in one message, or surface setup_page). What's missing is any named alternative sibling or a clear when-not condition.

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