Skip to main content
Glama

get_monitor_run

Retrieve the status and summary of an Airlock Monitor run using its run ID and API key, so you can check whether it is queued, running, completed, or failed.

Instructions

Get the status and summary of an Airlock Monitor run. Status is one of: queued, running, completed, failed.

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": {
      "api_key": "<api_key>",
      "run_id": "<run_id>"
    },
    "name": "get_monitor_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run id (from start_monitor_run).
api_keyYesAirlock Monitor API key (starts with amk_).
base_urlNoBase URL of the Monitor instance (default: https://app.shipsealed.com).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the possible status values (queued, running, completed, failed), which conveys that runs are asynchronous and may need polling. However, it does not explain what the 'summary' contains, whether reads are eventually consistent, or any rate/permission constraints beyond the api_key parameter.

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?

Two tight sentences with no filler: the purpose is front-loaded and the status enumeration follows immediately. It is efficient, though the brevity contributes to gaps addressed under contextual completeness.

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 simple three-parameter read tool, the core purpose and status values are covered, and the schema fully documents inputs. But with no output schema, the description should say more about what the returned 'summary' includes and whether the caller is expected to poll while status is queued or running.

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?

Schema description coverage is 100%, so all three parameters are already documented in the schema, including the run_id's origin and the api_key prefix. The description adds no additional parameter meaning or formatting detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource: retrieve 'the status and summary of an Airlock Monitor run,' and clarifies what status means by enumerating the four possible values. This is clear enough to distinguish it from siblings like get_monitor_findings or get_monitor_attestation, though it never explicitly contrasts itself with alternatives.

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 only implied: the run_id parameter description says it comes 'from start_monitor_run,' which hints this is the follow-up/polling call. There is no explicit statement about when to call this versus other sibling tools, nor when not to call it.

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