Skip to main content
Glama

SDR Autopilot status

sdr_get_autopilot

Autopilot of one SDR process: on/off, queue gap vs target, and the journal of recent runs with the levers each run pulled (revive sleeping hunters, re-judge uncertain contacts, open a second decision-maker, top up LinkedIn). ON by default for every launched process. Read-only, free.

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>"
    },
    "name": "sdr_get_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the two traits that matter most for an unannotated tool: it is read-only and free of cost. It also reveals the default state (ON for every launched process), which is non-obvious behavioral context. Gaps remain: no statement of what 'recent runs' means in volume, and no permission or rate-limit notes.

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?

Front-loaded with the core identity and return contents, followed by two short operational facts. The parenthetical list of levers is longer than strictly necessary but earns its place by telling the agent what the journal contains.

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 and no annotations, the description adequately substitutes by enumerating the return shape (state, queue gap vs target, run journal). What it omits is how the caller supplies the process id and how many runs the journal covers, which is a modest gap for a single-parameter read tool.

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?

There is one parameter (search_id, UUID) with 0% schema description coverage, so the description must compensate. 'Autopilot of one SDR process' only indirectly signals that the argument identifies a single process; it never names search_id, its UUID format, or where to obtain the id. Marginal compensation over the bare schema.

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?

Names a specific resource ('Autopilot of one SDR process') and enumerates the concrete payload: on/off state, queue gap vs target, and the journal of recent runs with the levers each run pulled. An agent can distinguish this read-status tool from sdr_run_autopilot/sdr_set_autopilot by the 'on/off ... journal of recent runs' framing, though it never names those siblings explicitly.

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?

Implies usage ('Read-only, free', 'ON by default for every launched process') so an agent can infer this is the inspection counterpart to mutating/run siblings, but there is no explicit 'use this when you want X; use sdr_set_autopilot to change it' routing. The reader must infer the alternative from names alone.

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