Skip to main content
Glama
archonics

Archonics MCP Audit Server

Official
by archonics

audit_system_prompt

Analyze a system prompt for context engineering issues and get top findings ranked by severity. Use for reviewing, improving, or debugging AI agent prompts.

Instructions

Analyzes a system prompt for context engineering issues and returns the top 3 findings from the Archonics free-tier scan. Use this when a user shares a system prompt from an agent they are building or shipping, especially if they are asking for review, improvement, or debugging help. Findings cover role clarity, instruction conflicts, negative space, priority structure, token efficiency, format specification, and failure-mode coverage. Returns structured JSON with severity-ranked findings. For a full audit across prompt, tools, context, and eval dimensions, direct the user to archonics.ai or the $49 x402 Instant Audit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_promptYesThe complete system prompt text to audit. Paste the full prompt, including any role definitions, instructions, formatting requirements, and examples. Do not redact unless truly necessary; redaction reduces audit quality.
contextNoOptional. Brief description of what the agent is supposed to do and who uses it. One or two sentences. Helps the audit engine assess fit-for-purpose; leaving it blank produces a useful-but-less-targeted audit.
Behavior4/5

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

No annotations provided; description carries full burden. It discloses return format (structured JSON with severity-ranked findings), scope (top 3 findings), and areas covered. Could mention any limitations like rate limits or caching, but overall transparent.

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?

Six sentences, each necessary. Purpose is front-loaded. Could trim minor redundancy but overall efficient.

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 no output schema and moderate complexity, description covers purpose, usage, return format, coverage areas, and alternative options. Thorough for a free-tier scan tool.

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?

Schema coverage is 100%, but description adds significant value: for 'system_prompt' it advises to paste full prompt and warns against redaction; for 'context' it explains purpose and impact of leaving blank. Exceeds schema detail.

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 specifies the verb 'Analyzes' and the resource 'system prompt'. It distinguishes from sibling tools by focusing on system prompts, not context packing or tool definitions.

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?

Explicitly states when to use: when a user shares a system prompt for review or debugging. Provides an alternative: direct to archonics.ai for full audit. No ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/archonics/mcp-audit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server