> ## Documentation Index
> Fetch the complete documentation index at: https://docs.armature.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Tool reference

> The read-only tools the Armature MCP exposes

All tools are **read-only, non-destructive, and idempotent**, scoped to your workspace and its retention window. Responses include both readable JSON and structured content, and mirror what the dashboard shows.

## `list_mcp_servers`

Your registered production MCP servers, with connection metadata. No secrets are ever returned.

## `list_sessions`

Reconstructed agent sessions, newest first — each with its primary use case and latest judged outcome. Mirrors the [Sessions](/dashboard/sessions) page.

| Parameter              | Description                                                                          |
| ---------------------- | ------------------------------------------------------------------------------------ |
| `range`                | Time range to query.                                                                 |
| `view`                 | `all`, `succeeded`, `partial`, `failed`, `high_frustration`, `repeat`, or `flagged`. |
| `useCaseId` / `intent` | Filter to one use case or intent phrasing.                                           |
| `server`               | Filter to one MCP server.                                                            |
| `limit`                | Max sessions to return.                                                              |

## `get_session`

One session end-to-end: the intent, every call in order, classification, and the judge's verdict. This is [session replay](/dashboard/sessions#session-replay) as data.

| Parameter   | Description |
| ----------- | ----------- |
| `sessionId` | Required.   |

## `list_use_cases`

Use-case clusters with volume, pass rate, and share of traffic. Mirrors [Use cases](/dashboard/use-cases). On young workspaces it falls back to raw-intent grouping and says so.

| Parameter | Description                                     |
| --------- | ----------------------------------------------- |
| `range`   | Time range to query.                            |
| `sort`    | `volume`, `frustration`, `failure`, or `trend`. |
| `server`  | Filter to one MCP server.                       |
| `limit`   | Max use cases to return.                        |

## `list_issues`

Issues ranked by blast radius, with session KPIs, daily pass-rate buckets, cause category, and affected use cases. Mirrors [Issues](/dashboard/issues).

| Parameter | Description               |
| --------- | ------------------------- |
| `range`   | Time range to query.      |
| `status`  | `open` or `archived`.     |
| `server`  | Filter to one MCP server. |

## `get_issue`

One issue in full: root cause, in-range blast radius (sessions, tools, use cases, clients), and example sessions to replay.

| Parameter         | Description       |
| ----------------- | ----------------- |
| `issueId`         | Required.         |
| `range`, `server` | Optional scoping. |

## Prompts

**`triage_issues`** — "Rank this workspace's issues by blast radius, open the worst one, and show a session that hits it." A guided tour of `list_issues` → `get_issue` → `get_session`.