Skip to main content
Glama

MisarReach MCP Server

by io.github.Misar-AI

get_autopilot_status

Read-onlyIdempotent

Get the current progress and results of one autopilot run.

This is how you follow a run started by start_autopilot: call it with the runId, leaving time between polls. Reading status does not pause, stop, or alter the run in any way — it keeps going regardless, and there is no tool here to stop it.

Reads only and costs no credits, however often you call it. Requires an API key. A run still in progress is a normal answer, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesAutopilot run UUID

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds valuable behavioral context: reading status does not pause or stop the run, there is no stop tool, it costs no credits however often called, requires an API key, and an in-progress response is normal. This goes well beyond structured metadata and helps the agent set expectations.

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?

The description is front-loaded with the core purpose, then adds essential usage and behavioral notes without fluff. Every sentence earns its place, including the reassurance that in-progress is not an error.

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

Completeness5/5

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

Given the tool's simple signature, strong annotations, and no output schema, the description sufficiently covers what an agent needs: how to poll, cost implications, auth requirement, non-destructive behavior, and expected semantics for in-progress runs. No important usage gap is apparent.

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?

The schema already covers runId well with 'Autopilot run UUID' at 100% coverage. The description adds practical meaning by explaining that the runId comes from a run started by start_autopilot and that polling should be spaced out, which is useful behavioral guidance for the single parameter even if not strictly required.

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 clearly states the resource ('one autopilot run') and the action ('get the current progress and results'). It also distinguishes itself from siblings like list_autopilot_runs and start_autopilot by framing this as following a run started by start_autopilot with a runId.

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?

It explicitly says when to use this tool ('This is how you follow a run started by start_autopilot'), how to use it ('call it with the runId, leaving time between polls'), and what not to do: it does not pause, stop, or alter the run, and there is no tool here to stop it. It also clarifies that an in-progress run is a normal response, not an error.

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

All MisarReach MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Every tool targets a distinct resource and action: deals, leads, lists, autopilot runs, sales agent config, channels, and discovery. Even where tools share an entity, they are clearly differentiated (e.g., list_deals vs get_pipeline, update_deal vs move_deal_stage), with descriptions explicitly calling out when to use which.

Naming Consistency5/5

All 27 tools follow a strict verb_noun snake_case pattern: create, get, list, update, move, search, score, sync, start, submit, verify, etc. No mixed conventions or vague verbs—each name precisely signals its function.

Tool Count3/5

27 tools is on the heavier side and slightly exceeds the typical well-scoped range. However, the server covers multiple subdomains (deals, lead discovery, autopilot, sales agent, channels), so the count is justified by the breadth of the domain, though it feels dense.

Completeness4/5

Core lifecycles are covered: deals (create, list, update, move), leads (search, sync, list, enrich, score, verify, send), autopilot (start, list, status), sales agent (config, actions, process), and channels (status, update). Minor gaps include no delete tool for deals/leads and no stop-autopilot, but these are likely intentional and not blocking.

Resources