Skip to main content
Glama
Sign In
AIR MCP Server

AIR MCP Server

by VericyIO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List artifacts

air_list_artifacts
Read-only

List document-derived artifacts for a project to get artifact PIDs needed when starting an AIR risk assessment.

Instructions

List document-derived artifacts for a project. Use artifact pids in air_start_assessment. Requires projects:read.

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": {
      "projectPid": "<projectPid>"
    },
    "name": "air_list_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPidYes
includeArchivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the required scope (projects:read), which annotations do not carry. It does not disclose whether archived artifacts are excluded by default, which the includeArchived parameter implies.

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 short sentences, front-loaded with the action, and every clause carries information (scope, downstream use, permission). No filler.

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?

With no output schema and 0% parameter coverage, the description should carry more weight. It covers purpose, auth, and follow-up use, but leaves the archived/active default and parameter meanings unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters. 'For a project' loosely maps to projectPid, but includeArchived is never mentioned or explained, so the description does not compensate for the schema gap.

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: 'List document-derived artifacts for a project.' This distinguishes it from air_list_documents and air_get_artifact_text, though it never explicitly contrasts with those siblings.

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?

Gives the permission prerequisite ('Requires projects:read') and a downstream hint ('Use artifact pids in air_start_assessment'), which is real usage value. However, it offers no when-not guidance or explicit alternative among the many list/get siblings.

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

Deploy Server

Other Tools