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 topical maps of the project

list_topical_maps
Read-only

Every map built for the project, newest first, without their clusters — read one with get_topical_map.

Instructions

Every map built for the project, newest first, without their clusters — read one with get_topical_map.

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe project to work on — its id from list_projects. Required on every call, so that parallel conversations never read or write each other's project.

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.28
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "The project to work on — its id from list_projects. Required on every call, so that parallel conversations never read or write each other's project.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "projectId"
+]
  2. Addedv1.0.22

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavior beyond that: result ordering (newest first) and the fact that cluster data is omitted from the payload, which tells the agent not to expect nested children. It doesn't mention pagination or result caps, though the absence of paging params suggests full enumeration.

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?

A single sentence, front-loaded with the scope and payload constraint, ending with the routing pointer. Every clause carries information; nothing is wasted or repeated from structured fields.

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?

With an output schema present, return values needn't be spelled out, and annotations cover the read-only profile. The description supplies everything else an agent needs to choose and call this tool: scope, ordering, omitted fields, and the detail-tool alternative.

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?

Only one parameter (projectId) and schema coverage is 100%, so the schema already explains the id's provenance from list_projects and per-call requirement. The description adds nothing about parameters, which is acceptable given full schema documentation — baseline 3 applies.

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 (every topical map built for the project) with explicit scope, ordering (newest first), and payload shape (without their clusters). An agent can immediately distinguish this list operation from get_topical_map, which returns the detailed single map.

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 names the alternative: 'read one with get_topical_map.' Combined with 'every map ... without their clusters,' this sets a clear rule — use this tool for enumeration, the sibling for full detail including clusters. 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

Other Tools