Skip to main content
Glama
Sign In

Howseen

by ai.howseen
OverviewDiscussionsAdmin

Turn Autopilot on or off

set_autopilot
Idempotent

Turn Autopilot on (articles of the content plan go live on the connected site on their date, once they meet the quality bar and the brand's rules) or off (nothing publishes automatically). Same switch as Howseen > Content. Preview first (says where it would publish); confirm: true applies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "on": "<on>"
    },
    "name": "set_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYestrue = Autopilot ON, false = OFF.
brandNoBrand id, name or domain (from list_brands). Optional when the account has a single brand.
confirmNoLeave out (or false) to get a preview: nothing changes. Set true ONLY after the user approved that exact preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the description adds genuinely useful behavior the annotations cannot convey: the dry-run preview mode, the fact that nothing changes until confirm: true, and the conditional gating on quality bar and brand rules. It stops short of saying what happens to already-live articles when Autopilot is switched off, or whether overdue items publish retroactively on enable.

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?

One compact sentence with the on/off semantics front-loaded and the preview-then-confirm rule attached at the end. The nested parentheticals are dense but each contains operative information 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?

For a three-parameter, fully annotated toggle with no output schema, the description covers the essential workflow risk (accidental enablement) and the meaning of both states. Minor remaining gaps are the off-state side effects on scheduled content and any permission requirements.

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% and each parameter already carries its own description, so the baseline is 3. The description adds real meaning for 'confirm' by tying approval to an exact preview and clarifying that preview reveals where it would publish, but 'on' and 'brand' are not elaborated beyond the schema.

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 names a specific switch and spells out the concrete effect of each state: on means content-plan articles publish on their scheduled date subject to the quality bar and brand rules, off means nothing publishes automatically. That effect-level explanation is what separates this from a manual sibling like publish_article, so an agent can place it precisely.

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 an explicit operating protocol: preview first (nothing changes), then apply with confirm: true only after the user approves that exact preview. This is clear guidance for the call sequence, though it never explicitly contrasts the tool with publish_article or says what to do when the user wants a one-off publish instead.

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

All Howseen 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