prompteye-mcp

Official

by PROMPTEYE-SP-Z-O-O

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Read one audit

get_audit

Read-only

Instructions

One audit in full: every URL that was audited and, once checked, the nine content signals found on it. Call it after create_audit until status is no longer pending — each URL carries analysis null until its own check finishes. The totalCost on each URL is PromptEye's internal AI processing cost in USD, not a charge to the user, and is null until the audit finishes.

Input Schema

Name	Required	Description	Default
`auditId`	Yes	Id of the audit, as create_audit reports it.

Output Schema

Name	Required	Description
`id`	Yes
`status`	Yes	pending the moment it is requested; success once every URL succeeded, partial when only some did, error when none did.
`endDate`	Yes	When it finished, ISO 8601 in UTC. null = not finished yet.
`results`	Yes
`duration`	Yes	How long the audit took, in seconds.
`projectId`	Yes	The project this audit was billed to. null = run without one.
`startDate`	Yes	When the audit started, ISO 8601 in UTC.
`numberOfUrls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.28Oct 23, 2026
- addedOutput schema / properties / results / items / properties / totalCost / description
```
Added value: +"PromptEye's internal AI processing cost in USD, not a charge to the user. null until the audit finishes."
```
Addedv1.0.22Oct 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With readOnlyHint and openWorldHint already covering safety and scope, the description adds substantial behavioral context: polling behavior, per-URL `analysis` nulls until each check finishes, and `totalCost` semantics including that it is internal AI processing cost rather than a user charge. These details materially help an agent interpret the tool's results.

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 three compact sentences with no waste. It front-loads the primary behavior and then adds lifecycle and cost-meaning details in a logical order.

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 output schema, annotations, and single fully documented parameter, the description provides everything an agent needs: what it returns, polling expectations, null semantics during processing, and how to interpret `totalCost`. No critical context is missing.

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 coverage is 100%, and the single `auditId` parameter is already documented as coming from create_audit. The description adds no additional parameter syntax or constraints, so the schema does the heavy lifting and a baseline 3 is appropriate.

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 states a specific retrieval action: 'One audit in full,' with the audited URLs and their nine content signals. It clearly distinguishes this as the single-audit read tool used after create_audit, rather than a creation or usage-summary tool.

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

Usage Guidelines4/5

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

It gives explicit timing guidance: call after create_audit and continue until `status` is no longer `pending`. It does not mention alternatives such as get_audit_usage or when not to use this tool, so it falls short of a full when/when-not/alternatives statement.

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

Deploy Server