Skip to main content
Glama

Run SDR Autopilot now

sdr_run_autopilot

Trigger one Autopilot pass immediately instead of waiting for the daily schedule. The pass only tops up the queue towards its target (re-judge, revive, second decision-maker); it never launches outreach by itself and charges only the usual per-contact pricing for contacts it adds.

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_run_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries real weight and does so well: it discloses the bounded scope ("only tops up the queue towards its target"), the side effects that are explicitly excluded ("never launches outreach by itself"), and the billing consequence ("charges only the usual per-contact pricing for contacts it adds"). It stops short of permissions, rate limits, or how to observe results, which keeps it off a 5.

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 tight sentences with the timing and scope constraint front-loaded, then the safeguards and cost. Every clause adds information an agent needs; nothing is 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 one-parameter, no-output-schema, no-annotation tool, the description covers the operation's scope, its safety boundary, and its cost, which are the highest-risk unknowns. The remaining gap is the undefined required parameter, which the schema does not describe either.

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% and the description never mentions the single required parameter search_id, so the reader gets no explanation of what a search identifies or how the pass is scoped to it. The parameter name and uuid format are largely self-explanatory, which prevents a 1, but the description does not compensate for the coverage gap at all.

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?

"Trigger one Autopilot pass immediately instead of waiting for the daily schedule" gives a specific verb (trigger) and resource (Autopilot pass) plus the timing distinction that separates it from the scheduled variant. It does not name or contrast with close siblings such as sdr_run_now or sdr_preview_run_now, so an agent must infer the split rather than being told.

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?

The "instead of waiting for the daily schedule" clause implies the usage context (on-demand run of the same daily job), which is genuinely useful. However, there is no explicit when-not guidance, no mention of a preview alternative, and no note about whether repeat calls are safe or idempotent.

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