Skip to main content
Glama
benteigland11

cartograph-mcp

cg_help

Browse recovery topics for common Cartograph error states like sync issues or blocked checkins, then retrieve full resolution steps. Use action=list to see available topics and action=get to read detailed guidance.

Instructions

Recovery guidance for common Cartograph trouble states (e.g. local out of sync with cloud, checkin blocked, validation contamination, publish rejected). Use action=list to browse topics with one-line summaries, then action=get with a topic to read the full resolution. Reach for this before guessing when an agent is stuck on a Cartograph error state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYeslist returns available topics; get returns the full entry for one topic.
topicNoTopic slug for action=get (from the list output).
Behavior4/5

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

Describes non-destructive guidance retrieval, but lacks explicit statement about idempotency or side effects; however, no annotations exist so description carries burden.

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 purpose, no wasted words.

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?

Complete for a help tool with only two parameters and no output schema; mentions return types for list and get actions.

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?

Schema covers 100% with descriptions; description adds context by explaining the list/get workflow and relation to topic output.

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 clearly states it provides recovery guidance for Cartograph trouble states with specific examples and distinguishes actions list and get.

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 advises to use this tool before guessing on error states, and explains when to use list versus get.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benteigland11/cartograph-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server