Skip to main content
Glama

Switch SDR Autopilot on/off

sdr_set_autopilot

Turn the Autopilot of one SDR process on or off. Off = the queue is topped up only by the hunters' normal flow; nothing else changes.

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": {
      "search_id": "<search_id>",
      "enabled": "<enabled>"
    },
    "name": "sdr_set_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
search_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does usefully explain the consequence of the off state ("queue is topped up only by the hunters' normal flow; nothing else changes"), but the on state is left undescribed, and there is no word on permissions, idempotency, or whether the change is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the primary action is front-loaded ahead of the clarifying consequence. Nothing could be cut without losing signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter boolean toggle with no annotations and no output schema, the description covers the core action and one side effect but leaves the on-state semantics and all parameter detail undocumented. An agent could call it correctly, but would be guessing about the meaning of enabling.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and largely does not. It only obliquely implies that one parameter selects the SDR process ("one SDR process") and that the other is the on/off boolean; neither search_id's UUID identity nor the enabled flag's mapping is stated.

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?

"Turn the Autopilot of one SDR process on or off" gives a concrete verb pair and resource, and the scoping phrase "of one SDR process" separates it from the bulk-queue siblings (sdr_run_autopilot, sdr_set_hunters). It never names which sibling to use instead, so sibling differentiation is only implicit.

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: an agent can infer this is the toggle to reach for when changing a single SDR process's autopilot state. There is no explicit when-to-use/when-not, no mention of sdr_get_autopilot for reading current state, and no stated prerequisites.

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