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

prompteye-mcp

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

Regenerate one category of a topical map

regenerate_topical_map_cluster
Destructive

Replaces every article currently filed under one category of a map with a fresh set, without touching the rest of the map or its pillar page. The categories are the category values the map's clusters carry.

Instructions

Replaces every article currently filed under one category of a map with a fresh set, without touching the rest of the map or its pillar page. The categories are the category values the map's clusters carry.

Input Schema

NameRequiredDescriptionDefault
mapIdYesId of the map, as create_topical_map or list_topical_maps reports it.
categoryYesThe category to regenerate; every existing article under it is replaced.
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",
-  "category"
-]New value: +[
+  "projectId",
+  "mapId",
+  "category"
+]
  2. Addedv1.0.22

TDQS

A4/5.0
Behavior4/5

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

The annotations already disclose destructive, non-idempotent, open-world behavior; the description adds valuable scope detail by saying every article under the category is replaced while the rest of the map and pillar page are untouched. It stops short of explaining what 'fresh set' means, whether regeneration is reversible, or whether it incurs cost/time.

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 sentences, front-loaded with the destructive scope and followed by the category identification detail. Every sentence adds useful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with full schema coverage, an output schema, and clear annotations, the description supplies the key missing context: exactly what gets destroyed and what remains untouched. Additional details about generated output or reversibility would improve it, but nothing essential for correct invocation 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%, so the schema already defines all three parameters. The description adds a small amount of meaning for the category parameter by explaining that categories are the values carried by the map's clusters, but it does not add syntax, format, or validation guidance beyond that.

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 verb and resource — replacing every article under one map category — and explicitly scopes what is not touched: the rest of the map and its pillar page. That makes the operation distinguishable from broader topical-map siblings like create_topical_map or get_topical_map.

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

Usage Guidelines3/5

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

It implies when to use the tool by describing category-level regeneration and explains where category values come from, but it does not explicitly compare against alternatives such as creating a new map or editing articles individually. No prerequisites or exclusions are stated.

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