ism-mcp

Overview Schema Source Related Servers Discussions Admin

ism_coverage_read

Read-only

Retrieves coverage data from a project's ISM coverage manifest, displaying scope, summary counts, and curated entries. Optionally filter controls by status such as covered or partial.

Instructions

Read the project's coverage manifest (.ism-coverage.toml). Never writes.

Returns scope, summary counts, and curated entries. Walks up from cwd to find the manifest if project_path is omitted and fails when none is found. status_filter narrows the controls map to a single status (covered|partial|not-applicable|deferred) while summary stays unfiltered. To see what is missing rather than what is curated, use ism_coverage_gaps.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project_path`	No
`status_filter`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	Yes
`project`	Yes
`summary`	Yes
`controls`	Yes
`warnings`	Yes
`manifest_path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv1.1.1Jul 6, 2026

changedInput schema / properties / status_filter / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "covered",
+      "partial",
+      "not-applicable",
+      "deferred"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / $defs

Added value: +{
+  "CoverageEntry": {
+    "properties": {
+      "attachments": {
+        "items": {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        "title": "Attachments",
+        "type": "array"
+      },
+      "commits": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Commits",
+        "type": "array"
+      },
+      "files": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Files",
+        "type": "array"
+      },
+      "how_met": {
+        "title": "How Met",
+        "type": "string"
+      },
+      "last_reviewed": {
+        "title": "Last Reviewed",
+        "type": "string"
+      },
+      "next_review": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Next Review"
+      },
+      "reviewed_against": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Reviewed Against"
+      },
+      "reviewed_by": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Reviewed By"
+      },
+      "status": {
+        "title": "Status",
+        "type": "string"
+      },
+      "urls": {
+        "items": {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        "title": "Urls",
+        "type": "array"
+      }
+    },
+    "required": [
+      "status",
+      "how_met",
+      "last_reviewed",
+      "reviewed_against",
+      "reviewed_by",
+      "next_review",
+      "files",
+      "commits",
+      "urls",
+      "attachments"
+    ],
+    "title": "CoverageEntry",
+    "type": "object"
+  }
+}

addedOutput schema / properties / controls

Added value: +{
+  "additionalProperties": {
+    "$ref": "#/$defs/CoverageEntry"
+  },
+  "title": "Controls",
+  "type": "object"
+}

addedOutput schema / properties / manifest_path

Added value: +{
+  "title": "Manifest Path",
+  "type": "string"
+}

addedOutput schema / properties / project

Added value: +{
+  "additionalProperties": true,
+  "title": "Project",
+  "type": "object"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / scope

Added value: +{
+  "additionalProperties": true,
+  "title": "Scope",
+  "type": "object"
+}

addedOutput schema / properties / summary

Added value: +{
+  "additionalProperties": {
+    "type": "integer"
+  },
+  "title": "Summary",
+  "type": "object"
+}

addedOutput schema / properties / warnings

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

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "manifest_path",
+  "scope",
+  "project",
+  "summary",
+  "controls",
+  "warnings"
+]

changedOutput schema / title

Previous value: -"ism_coverage_readOutput"New value: +"CoverageReadResult"

First observedv1.1.0Jun 4, 2026

TDQS

A5/5.0

Behavior5/5

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

The description states 'Never writes', which aligns with the `readOnlyHint` annotation. It further details that `status_filter` narrows the controls map but leaves the summary unfiltered, adding behavioral insight beyond the annotations.

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?

The description is concise and well-structured. The core function is stated upfront, followed by succinct parameter explanations and a clear sibling alternative reference. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only two parameters, an output schema, and clear annotations, the description covers all necessary aspects: purpose, parameters, behavior, and alternatives. It is complete for an AI agent to select and invoke correctly.

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

Parameters5/5

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

Despite 0% schema description coverage, the description fully explains both parameters: `project_path` behavior (walk-up from cwd) and `status_filter` acceptable values and effect (filters controls map, not summary). This compensates the missing schema descriptions completely.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool reads the project's coverage manifest, specifying the resource (`.ism-coverage.toml`) and the action. It also distinguishes itself from a sibling tool, `ism_coverage_gaps, by clarifying that this tool returns curated entries while the sibling shows missing items.

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool versus the alternative `ism_coverage_gaps`. It also explains the behavior when `project_path` is omitted (walks up from cwd) and fails if not found, providing clear context for usage.

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

Deploy Server