Skip to main content
Glama

get_monitor_findings

Retrieve leaks and warnings from a completed Airlock Monitor run, including severity, affected object details, and suggested SQL fixes for remediation.

Instructions

Get the findings (leaks, warnings) from a completed Airlock Monitor run. Each finding has kind, severity, object, detail and a suggested SQL fix.

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

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run id of a completed 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

A3.6/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 behavioral burden. It correctly signals a read-only retrieval scoped to a completed run and enumerates the returned fields (kind, severity, object, detail, SQL fix), which is valuable given there is no output schema; but it says nothing about pagination, result limits, or failure behavior when the run is incomplete or the key is invalid.

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: the action and scope come first, followed by the shape of the returned data. No filler, no restatement of the tool name.

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 simple read tool with full schema coverage and no output schema, the description covers the essentials and usefully enumerates return fields. The main gap is the absence of any signal about how this differs from sibling retrieval tools and how partial/empty results are handled.

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%, with run_id, api_key, and base_url all documented in the schema. The description adds no additional meaning about parameter formats, id shape, or defaults, 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?

The description names a concrete verb and resource ('Get the findings ... from a completed Airlock Monitor run') and clarifies what a finding contains. It is clear on its own but does nothing to distinguish it from the sibling 'get_findings', leaving the agent to guess which retrieval tool applies.

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 phrase 'completed ... run' implies a precondition (the run must be finished), which is useful context. However, there is no explicit when-to-use guidance, no statement about what happens for an in-progress run, and no routing versus related tools like get_findings, get_monitor_run, or explain_finding.

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