prompteye-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Tell the PromptEye team about a missing capability

report_missing_capability

Notify the PromptEye team when a user needs a capability the server or API cannot provide. Requires user confirmation before sending.

Instructions

Sends the PromptEye team a short note that the user needs something this server or the PromptEye API cannot do today.

Use it only when the user wants the PromptEye team to know about the gap. Ask the user first and send nothing until they agree in this conversation; never send a report on your own initiative.

Send only a short description of the need and of what you were trying to do. Never include conversation transcripts, quoted messages, figures from the workspace or personal data such as names, email addresses or phone numbers.

Input Schema

TableJSON Schema

Name	Required	Description
`need`	Yes	What the user needs that the server cannot do, in a few plain sentences. No transcripts and no personal data.
`attemptedAction`	Yes	What you were trying to do for the user when you hit the gap, in one short sentence.
`confirmedByUser`	Yes	Must be true, and only set it once the user has explicitly agreed in this conversation to send this report to the PromptEye team.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`receivedAt`	Yes	When PromptEye received the report, ISO 8601 in UTC.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.22Oct 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations alone only say readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds the behaviorally critical facts: this transmits to an external party, it is consent-gated per conversation, and it must never contain transcripts, workspace figures, or personal data. That is substantial disclosure beyond the structured fields.

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?

Three short paragraphs, front-loaded with purpose then the consent condition then the content limits. Every sentence carries a distinct operational rule; no filler.

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?

For a consent-gated outbound-report tool with full schema coverage and an output schema, the description covers purpose, gating condition, and content restrictions. Nothing an agent needs in order to invoke it safely 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 description coverage is 100%, so all three parameters (need, attemptedAction, confirmedByUser) are already documented, and the description largely restates those constraints (short description, no personal data, user must confirm). Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb+resource+recipient: sends the PromptEye team a note about a capability gap. This is trivially distinguishable from every sibling tool, which are all workspace/data operations rather than outbound user-initiated messages.

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?

Explicit when-to-use ('only when the user wants the PromptEye team to know about the gap'), explicit prerequisite ('ask the user first', 'send nothing until they agree in this conversation'), and an explicit prohibition ('never send a report on your own initiative'). Nothing is left to inference.

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

Deploy Server