AirMCP

by heznpc

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Profile Status

profile_status

Read-onlyIdempotent

Show the active AirMCP profile, module set, tool exposure mode, exposed tool count, and total registered tool count.

Instructions

Show the active AirMCP profile, module set, tool exposure mode, exposed tool count, and total registered tool count.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`profile`	Yes
`toolExposure`	Yes
`toolsExposed`	Yes
`frontDoorTools`	Yes
`harnessAdapter`	Yes
`modulesEnabled`	Yes
`modulesDisabled`	Yes
`toolsRegistered`	Yes
`workflowReadiness`	Yes
`requireToolSession`	Yes
`toolSessionsActive`	Yes
`modulesMissingPacks`	Yes
`modulePacksAvailable`	Yes
`modulePacksConfigured`	Yes
`missingPackInstallHints`	Yes
`modulePackInstallIssues`	Yes
`modulesMissingAddonPackages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.16.6Oct 22, 2026
- removedOutput schema / properties / modulePackInstallIssues / items / properties / command / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / modulePackInstallIssues / items / properties / command / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / modulePackInstallIssues / items / properties / installedVersion / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / modulePackInstallIssues / items / properties / installedVersion / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedv2.16.5Aug 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedv2.16.2Jul 30, 2026

addedOutput schema / properties / workflowReadiness

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "blocked": {
+      "type": "number"
+    },
+    "partial": {
+      "type": "number"
+    },
+    "ready": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "ready",
+    "partial",
+    "blocked"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "profile",
-  "toolExposure",
-  "modulePacksConfigured",
-  "modulePacksAvailable",
-  "modulesMissingPacks",
-  "modulesMissingAddonPackages",
-  "modulePackInstallIssues",
-  "missingPackInstallHints",
-  "requireToolSession",
-  "harnessAdapter",
-  "modulesEnabled",
-  "modulesDisabled",
-  "toolsExposed",
-  "toolsRegistered",
-  "toolSessionsActive",
-  "frontDoorTools"
-]New value: +[
+  "profile",
+  "toolExposure",
+  "modulePacksConfigured",
+  "modulePacksAvailable",
+  "modulesMissingPacks",
+  "modulesMissingAddonPackages",
+  "modulePackInstallIssues",
+  "missingPackInstallHints",
+  "requireToolSession",
+  "harnessAdapter",
+  "modulesEnabled",
+  "modulesDisabled",
+  "toolsExposed",
+  "toolsRegistered",
+  "toolSessionsActive",
+  "frontDoorTools",
+  "workflowReadiness"
+]

Changed9 schema fields changedv2.14.1Jul 4, 2026

addedOutput schema / properties / harnessAdapter
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / missingPackInstallHints

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "command": {
+        "type": "string"
+      },
+      "installSpec": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "modules": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "pack": {
+        "type": "string"
+      },
+      "packageName": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "pack",
+      "packageName",
+      "installSpec",
+      "modules",
+      "command",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / modulePackInstallIssues

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "command": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "expectedVersion": {
+        "type": "string"
+      },
+      "installStatus": {
+        "type": "string"
+      },
+      "installedVersion": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "message": {
+        "type": "string"
+      },
+      "pack": {
+        "type": "string"
+      },
+      "packageName": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "pack",
+      "packageName",
+      "installStatus",
+      "installedVersion",
+      "expectedVersion",
+      "command",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / modulePacksAvailable

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / modulePacksConfigured
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / modulesMissingAddonPackages

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / modulesMissingPacks

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / requireToolSession
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "profile",
-  "toolExposure",
-  "modulesEnabled",
-  "modulesDisabled",
-  "toolsExposed",
-  "toolsRegistered",
-  "toolSessionsActive",
-  "frontDoorTools"
-]New value: +[
+  "profile",
+  "toolExposure",
+  "modulePacksConfigured",
+  "modulePacksAvailable",
+  "modulesMissingPacks",
+  "modulesMissingAddonPackages",
+  "modulePackInstallIssues",
+  "missingPackInstallHints",
+  "requireToolSession",
+  "harnessAdapter",
+  "modulesEnabled",
+  "modulesDisabled",
+  "toolsExposed",
+  "toolsRegistered",
+  "toolSessionsActive",
+  "frontDoorTools"
+]

Addedv2.14.0Jun 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is fully covered. The description adds that it reflects the currently active/loaded state, but nothing about staleness, cost, or whether state changes between calls.

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?

A single front-loaded sentence with no filler. The enumerated field list is somewhat redundant given an output schema exists, but it is short enough not to hurt.

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?

With no parameters, full annotations, and an output schema describing the return value, the description covers what an agent needs to invoke it. The only real gap is routing guidance relative to list_profiles and tool_session_status.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The schema is trivially complete for an empty object.

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 ('Show') and enumerates exactly what is reported: active profile, module set, tool exposure mode, exposed vs total tool counts. It is clear what the tool does, but it never distinguishes itself from the similar-sounding siblings list_profiles and tool_session_status.

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 guidance on when to call this versus list_profiles or tool_session_status, both of which appear to report related configuration/session state. Usage is only implicit from the word 'active'.

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