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

prompteye-mcp

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

Read one topical map

get_topical_map
Read-only

One map in full: its pillar page and every cluster article, grouped by category. Call it after create_topical_map until status is ready — pillar is null and clusters is empty until then, and errorMessage is set instead if…

Instructions

One map in full: its pillar page and every cluster article, grouped by category. Call it after create_topical_map until status is ready — pillar is null and clusters is empty until then, and errorMessage is set instead if generation failed.

Input Schema

NameRequiredDescriptionDefault
mapIdYesId of the map, as create_topical_map or list_topical_maps reports it.
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
idYes
topicYes
pillarYesThe compendium page. null until ready.
statusYesprocessing the moment it is requested, then ready — pillar and clusters filled in — or error, see errorMessage.
clustersYesThe supporting article titles, grouped by category. Empty until ready.
languageYes
createdAtYesWhen the map was requested, ISO 8601 in UTC.
projectIdYes
errorMessageYesWhy generation failed. null unless status is error.
generationCostYesCost of the generation, in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.28
    • 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"
+}
    • changedInput schema / required
      Previous value: -[
-  "mapId"
-]New value: +[
+  "projectId",
+  "mapId"
+]
  2. Addedv1.0.22

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds genuinely new behavioral context: pillar is null and clusters empty until status is ready, and errorMessage is set instead on generation failure. That polling/lifecycle contract is exactly the kind of detail annotations cannot convey.

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?

Two tight sentences: the first front-loads what is returned, the second immediately covers the lifecycle precondition and failure state. No filler, no restatement of the title.

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?

Output schema exists so return shape needn't be explained, but the description still supplies the readiness semantics an agent needs to poll correctly, which is the one thing the schema cannot express. Nothing required for a correct call 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%, with mapId and projectId both documented in-schema including their provenance (create_topical_map/list_topical_maps, list_projects) and the isolation rationale. The description adds no parameter-level meaning beyond this, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource ('one map in full') and enumerates its contents — pillar page plus every cluster article grouped by category — so an agent knows exactly what this returns versus a list tool. It stops short of explicitly contrasting with list_topical_maps, which keeps it from a 5.

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?

Gives a concrete call condition: use it after create_topical_map, repeatedly, until `status` is `ready`. That is real when-to-use guidance rather than implied usage. It does not state when to prefer list_topical_maps or what to do if the map id is unknown, so it is not fully explicit about alternatives.

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