Skip to main content
Glama
PROMPTEYE-SP-Z-O-O

prompteye-mcp

Official
by PROMPTEYE-SP-Z-O-O
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List the PromptEye help articles

list_help_articles
Read-only

PromptEye's own knowledge base (https://app.prompteye.com/help, index at https://app.prompteye.com/help/index.md): guides on how the product works.

Instructions

PromptEye's own knowledge base (https://app.prompteye.com/help, index at https://app.prompteye.com/help/index.md): guides on how the product works. Use it when the user asks how something in PromptEye works, what a setting, score or feature means, how to connect or configure something, how to do something in the app — or reports a problem or something unexpected, such as getting the same report again, a report with no score or an email that did not arrive, which the guides usually explain — public reports, the report score, leads, projects made from reports, connecting a form, notifications, branding. Pick the article whose title fits, then read it with read_help_article.

This is documentation, not the user's data: for their visibility, prompts or competitors use the other tools. Every article has a page for people; give the user that link when you answer.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
homeYes
articlesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.22
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "articles": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "path": {
+            "type": "string"
+          },
+          "section": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "section",
+          "title",
+          "path",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "home": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "home",
+    "articles"
+  ],
+  "type": "object"
+}
  2. Addedv1.0.20

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly and openWorld. The description adds meaningful context beyond them: that results are documentation rather than tenant data, that each article has a human-facing page whose link should be given to the user, and that article selection is by title matching. It does not mention result volume or whether there is pagination, which is a minor gap for a zero-parameter listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core routing information is front-loaded, but the middle is an overlong run-on sentence with a sprawling comma list of topics ('public reports, the report score, leads, projects made from reports, connecting a form, notifications, branding') that repeats what the earlier clause already covered. It is informative but could be shortened by a third without loss.

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?

An output schema exists, so return values need not be explained. Given zero parameters and read-only annotations, the description supplies everything an agent needs: what the corpus covers, when to route to it, how to select an article, what to do next, and what to give the user.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the call is parameterless by telling the agent to filter by reading titles rather than passing arguments.

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 resource (PromptEye's own help/knowledge-base articles) with concrete URLs, and makes clear it is a listing step that feeds read_help_article. An agent can distinguish it from read_help_article and from data tools like list_reports without opening any schema.

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?

Gives explicit triggering conditions (user asks how a setting/score/feature works, how to connect something, or reports an unexpected result such as a missing email or unscored report) and an explicit exclusion: 'This is documentation, not the user's data: for their visibility, prompts or competitors use the other tools.' It also prescribes next step: pick the article whose title fits, then read it with read_help_article.

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

Deploy Server

Other Tools