Skip to main content
Glama

list_monitor_projects

List Supabase projects connected to your Airlock Monitor account and retrieve each project's ID, label, and last-run timestamp for audit tracking.

Instructions

List the Supabase projects connected to your Airlock Monitor account. Returns project id, label, and last-run timestamp for each.

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

Input Schema

NameRequiredDescriptionDefault
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?

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses what is returned (project id, label, last-run timestamp), which compensates for the absent output schema, but it says nothing about whether the call is read-only and side-effect free, whether results are paginated or capped, or how an empty account is reported.

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 identity of the resource front-loaded and the return shape second. Nothing is redundant with the title or schema, and no sentence could be removed without losing content.

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 two-parameter read tool with no output schema, this covers the essentials: what is listed, whose account it is scoped to, and which fields come back. Only pagination/result-limit behavior and read-only reassurance are missing, which are minor for this complexity level.

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 both api_key (amk_ prefix) and base_url (default instance URL) fully documented in the schema itself. The description adds no additional meaning about either parameter, 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?

The description opens with a specific verb and resource: 'List the Supabase projects connected to your Airlock Monitor account.' That is materially more informative than the name alone and separates it from siblings like get_monitor_run or get_monitor_findings, which operate on runs/findings rather than the project inventory. It stops short of explicitly contrasting itself with any sibling, so a 4 rather than a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. It is only implied that this is a discovery call, e.g. to obtain project ids before invoking get_monitor_run or start_monitor_run, but the description never says that or states any prerequisite beyond the api_key parameter already documented in the schema.

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