Skip to main content
Glama
Sign In

Rankwise

by com.tryrankwise
OverviewDiscussionsAdmin

Change autopilot settings

set_autopilot
DestructiveIdempotent

Change the workspace's content autopilot. mode: off, draft_only (only suggests briefs, spends nothing) or requires_approval (approves up to the weekly quota of suggested briefs, which spends credits, and holds every draft for review). weekly_quota is capped by the plan. paused pauses or resumes. Auto-publishing (full_auto) cannot be switched on here; do that in the Rankwise app.

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": "set_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNofull_auto is refused: switch on auto-publishing in the app.
pausedNo
weekly_quotaNo

Output Schema

NameRequiredDescriptionDefault
modeNo
updatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the description's added value is the credit-spending consequence of each mode, the plan-capped quota, and the refusal of full_auto. It does not explain side effects on existing briefs/drafts or what turning off autopilot leaves behind, which matters for a destructive-flagged tool.

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?

Compact and front-loaded, opening with the core action before detailing modes. Dense but almost every clause carries new information; only the quoted mode labels are slightly verbose relative to the enum.

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 an output schema present, return values need not be described, and the description covers the mode semantics, quota constraint, and the full_auto escape hatch. It does not clarify whether omitted parameters are left unchanged or reset, a notable gap for a partial-update tool with zero required parameters.

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 only 33% (mode alone is documented), so the description must carry paused and weekly_quota. It does: 'paused pauses or resumes' and 'weekly_quota is capped by the plan', which adds a plan-constraint beyond the schema's 1-7 range.

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 ('Change the workspace's content autopilot'), which cleanly separates it from the read-only sibling get_autopilot. The mode enumeration immediately clarifies the scope of what 'change' means here.

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

Usage Guidelines5/5

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

Explicitly maps each mode to its behavior and cost: draft_only 'spends nothing', requires_approval 'spends credits' and holds drafts for review. It also gives an explicit when-not path by telling the agent full_auto must be enabled in the Rankwise app instead.

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

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