Skip to main content
Glama

start_monitor_run

Launch an Airlock Monitor audit (RLS + DAST) on a connected project; returns run ID and initial status to poll with get_monitor_run.

Instructions

Start an Airlock Monitor run (RLS audit + DAST) on a connected project. Returns the run id and initial status. Poll with get_monitor_run.

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

Input Schema

NameRequiredDescriptionDefault
api_keyYesAirlock Monitor API key (starts with amk_).
base_urlNoBase URL of the Monitor instance (default: https://app.shipsealed.com).
project_idYesThe project id to run against (from list_monitor_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the async pattern (returns run id and initial status, then poll) which is the key operational behavior, but says nothing about cost, run duration, concurrency limits, or what happens to a prior run if one is started again.

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?

Three short sentences with zero waste: verb+resource first, then what is returned, then the follow-up action. Perfectly front-loaded.

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 3-parameter tool with no output schema, the description covers what matters: target, return shape (run id + initial status), and the polling follow-up. Missing only failure/permission conditions and any note on run cost or duplication.

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 coverage is 100% and each parameter already documents itself (api_key format, default base_url, project_id sourced from list_monitor_projects). The description adds nothing beyond the schema, so the baseline 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+resource ('Start an Airlock Monitor run') and defines what the run contains (RLS audit + DAST) and its target ('a connected project'). It also names the sibling to poll with (get_monitor_run), though it does not differentiate itself from audit_supabase_rls, which overlaps on the RLS-audit part.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context: the project must be connected, and the agent is told to poll with get_monitor_run rather than wait on this call. There is no explicit when-not guidance (e.g., don't start a second run while one is active, or when to prefer audit_supabase_rls).

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