# analyze_manifest

Score CLAUDE.md / AGENTS.md manifest content with the same rules as the Clarx manifest studio. Returns an overall quality estimate (0-100), per-pillar scores, findings with line numbers, and a section checklist. This is a manifest quality estimate — do not compare it to Clarx repo AI-readiness scores, which use a different rule system.

Agent View of the PolicyLayer registry record for `analyze_manifest`. HTML page: https://policylayer.com/tools/ai-clarx-mcp/analyze-manifest

## Facts

- Tool: `analyze_manifest`
- Server: Mcp (`@clarxai/mcp`) — https://policylayer.com/tools/ai-clarx-mcp.md
- Install: `npx -y @clarxai/mcp`
- Homepage: https://github.com/Gernika-Labs/clarx-cloud
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `content` | string | no | Full markdown body of the manifest. Pass this or file_path, not both. |
| `file_path` | string | no | Path to the manifest file (resolved against the server working directory, typically the workspace root). Preferred — avoids inlining the file into the conversat |
| `include_outline` | boolean | no | Include the heading outline (section tree with line numbers). |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "analyze_manifest",
    "arguments": {}
  }
}
```

## Why analyze_manifest is rated Low

This tool retrieves and analyzes manifest data to provide a quality assessment. It does not create, modify, delete, or execute any operations—it only reads manifest files and returns analytical results. The retrieval and scoring of manifest content with no side effects places it firmly in the Read category.

From the tool's own definition: "The tool 'analyze_manifest' scores and analyzes manifest content, returning quality estimates, per-pillar scores, findings, and checklists."

Risk signals: Accepts file system path (file_path) · Accepts raw HTML/template content (content)

## Use case

AI agents call analyze_manifest to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_manifest": {}
  }
}
```

## Other tools on Mcp (4)

- `analyze_clarx_manifest` — Read — https://policylayer.com/tools/ai-clarx-mcp/analyze-clarx-manifest.md
- `generate_manifest_draft` — Write — https://policylayer.com/tools/ai-clarx-mcp/generate-manifest-draft.md
- `get_ci_workflow` — Write — https://policylayer.com/tools/ai-clarx-mcp/get-ci-workflow.md
- `suggest_manifest_fix` — Write — https://policylayer.com/tools/ai-clarx-mcp/suggest-manifest-fix.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ai-clarx-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-clarx-mcp