Replai

Inspect Agent readiness

agent_setup_read

Read-onlyIdempotent

Reports readiness, pending draft/live changes, source versions and advisory tests.

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	Agent ID from agents_list or agent_create.

Output Schema

Name	Required	Description	Default
`tests`	Yes
`status`	Yes
`pending`	Yes
`sources`	Yes
`agent_id`	Yes
`readiness`	Yes
`draft_revision`	Yes
`publish_version`	Yes
`source_versions`	Yes
`published_revision`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

addedOutput schema / $defs / TestResult / properties / accepted_at

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Accepted At"
+}

Changed1 schema field changedOct 30, 2026
- addedInput schema / properties / agent_id / description
```
Added value: +"Agent ID from agents_list or agent_create."
```

Changed4 schema fields changedOct 30, 2026

addedOutput schema / $defs / RepositorySelectedFile

Added value: +{
+  "properties": {
+    "path": {
+      "title": "Path",
+      "type": "string"
+    },
+    "sha": {
+      "title": "Sha",
+      "type": "string"
+    },
+    "size": {
+      "title": "Size",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "path",
+    "sha",
+    "size"
+  ],
+  "title": "RepositorySelectedFile",
+  "type": "object"
+}

addedOutput schema / $defs / RepositorySelection

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "excluded_paths": {
+      "items": {
+        "type": "string"
+      },
+      "maxItems": 100,
+      "title": "Excluded Paths",
+      "type": "array"
+    },
+    "files": {
+      "items": {
+        "$ref": "#/$defs/RepositorySelectedFile"
+      },
+      "title": "Files",
+      "type": "array"
+    },
+    "included_paths": {
+      "items": {
+        "type": "string"
+      },
+      "maxItems": 100,
+      "title": "Included Paths",
+      "type": "array"
+    },
+    "rule": {
+      "anyOf": [
+        {
+          "enum": [
+            "customer_docs",
+            "docs_directory",
+            "docs_site:mkdocs",
+            "docs_site:docusaurus",
+            "docs_site:mintlify",
+            "docs_site:vitepress",
+            "docs_site:starlight",
+            "docs_site:gitbook",
+            "docs_site:sphinx"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Rule"
+    },
+    "skipped_count": {
+      "default": 0,
+      "title": "Skipped Count",
+      "type": "integer"
+    },
+    "skipped_files": {
+      "items": {
+        "$ref": "#/$defs/RepositorySkippedFile"
+      },
+      "title": "Skipped Files",
+      "type": "array"
+    }
+  },
+  "title": "RepositorySelection",
+  "type": "object"
+}

addedOutput schema / $defs / RepositorySkippedFile

Added value: +{
+  "properties": {
+    "path": {
+      "title": "Path",
+      "type": "string"
+    },
+    "reason": {
+      "enum": [
+        "internal",
+        "excluded",
+        "not_published",
+        "file_too_large",
+        "unsupported_file"
+      ],
+      "title": "Reason",
+      "type": "string"
+    }
+  },
+  "required": [
+    "path",
+    "reason"
+  ],
+  "title": "RepositorySkippedFile",
+  "type": "object"
+}

addedOutput schema / $defs / SourceState / properties / repository_selection

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/RepositorySelection"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed4 schema fields changedOct 30, 2026

addedOutput schema / $defs / PendingChanges / properties / sources_removed / items / $ref
```
Added value: +"#/$defs/RemovedSource"
```
removedOutput schema / $defs / PendingChanges / properties / sources_removed / items / format
```
Removed value: -"uuid"
```
removedOutput schema / $defs / PendingChanges / properties / sources_removed / items / type
```
Removed value: -"string"
```

addedOutput schema / $defs / RemovedSource

Added value: +{
+  "description": "A source the next publication drops; name is None when no publication recorded it.",
+  "properties": {
+    "id": {
+      "format": "uuid",
+      "title": "Id",
+      "type": "string"
+    },
+    "name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Name"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "title": "RemovedSource",
+  "type": "object"
+}

First observedOct 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare this is a safe, read-only, idempotent operation, so the baseline is covered. The description adds useful scope by naming what is included in the report, but it does not disclose behavioral details such as whether results are aggregated, scoped, or cached.

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 a single front-loaded sentence with no wasted words. It efficiently lists the report contents and stays appropriately sized for a one-parameter read tool.

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?

An output schema exists, so the description does not need to explain return values, and the annotations carry the safety profile. The description covers the scope of the report well, though it could say more about when this aggregate view is preferable to reading drafts or sources individually.

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%, and the single agent_id parameter is fully documented in the schema with its source tools. The description itself adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb, "Reports," and enumerates the concrete contents: readiness, pending draft/live changes, source versions, and advisory tests. It is clear what the tool returns, though it does not explicitly distinguish itself from siblings such as agent_draft_read or source_read.

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?

The description gives no guidance on when to use this tool versus alternatives like agent_draft_read, source_read, or test_cases_list. The name implies inspection of agent setup, but the definition leaves selection entirely to inference.

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

All Replai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?