Skip to main content
Glama
robertZaufall

MindManager MCP Server

get_grounding_information

Extract central topics and selected subtopics from mind maps to provide structural context for analysis or processing.

Instructions

Extracts grounding information (central topic, selected subtopics) from the mindmap.

Args:
    mode (str): Detail level ('full', 'content', 'text'). Defaults to 'full'.
    turbo_mode (bool): Enable turbo mode (text only). Defaults to False.

Returns:
    Union[List[str], Dict[str, str]]: A list containing [top_most_topic, subtopics_string] or error dictionary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNofull
turbo_modeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary handler for the 'get_grounding_information' MCP tool. Registered via @mcp.tool() decorator. Handles parameters, calls helper function, serializes output, and manages errors.
    @mcp.tool()
    async def get_grounding_information(
        mode: str = 'full',
        turbo_mode: bool = False
    ) -> Union[List[str], Dict[str, str]]:
        """
        Extracts grounding information (central topic, selected subtopics) from the mindmap.
    
        Args:
            mode (str): Detail level ('full', 'content', 'text'). Defaults to 'full'.
            turbo_mode (bool): Enable turbo mode (text only). Defaults to False.
    
        Returns:
            Union[List[str], Dict[str, str]]: A list containing [top_most_topic, subtopics_string] or error dictionary.
        """
        try:
            print("Calling get_grounding_information()", file=sys.stderr)
            top_most, subtopics_str = _get_grounding_information(mode=mode, turbo_mode=turbo_mode)
            print(f"get_grounding_information() returned: top='{top_most}', subtopics='{subtopics_str}'", file=sys.stderr)
            return [top_most, subtopics_str] # Return as list for JSON
        except Exception as e:
            # This function doesn't directly call MindManager, so errors are less likely external
            print(f"ERROR in get_grounding_information: {e}", file=sys.stderr)
            return {"error": "Internal Error", "message": f"Failed to get grounding information: {e}"}
  • Supporting helper function that creates a MindmapDocument instance, retrieves the mindmap and selection, and calls the underlying get_grounding_information method on the document.
    def _get_grounding_information(mode='text', turbo_mode=True):
        document = _get_document_instance(turbo_mode=turbo_mode)
        if document.get_mindmap(mode=mode):
            document.get_selection()
            return document.get_grounding_information()
        return None
  • The @mcp.tool() decorator registers the get_grounding_information function as an MCP tool.
    @mcp.tool()
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool extracts information (a read operation) and hints at behavioral traits like different modes and turbo mode, but lacks details on permissions, error conditions, or side effects. It doesn't contradict annotations, but for a tool with no annotations, more behavioral context would be beneficial.

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

Conciseness4/5

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

The description is appropriately sized and front-loaded, starting with the core purpose followed by parameter and return details. Each sentence adds value, with no wasted words. The structure is clear, though the return type explanation could be slightly more concise.

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?

Given the tool's moderate complexity, no annotations, and an output schema that documents return types, the description is fairly complete. It covers purpose, parameters, and returns adequately. However, it lacks context on prerequisites (e.g., needing an open mindmap) and doesn't fully explain sibling differentiation, leaving minor gaps.

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 description adds significant meaning beyond the input schema, which has 0% description coverage. It explains the parameters 'mode' and 'turbo_mode' with details on allowed values ('full', 'content', 'text') and effects ('text only'), and specifies defaults. This compensates well for the schema's lack of descriptions, though it could clarify the exact differences between modes.

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 clearly states the tool's purpose: 'Extracts grounding information (central topic, selected subtopics) from the mindmap.' It specifies the verb ('extracts'), resource ('grounding information'), and source ('mindmap'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from siblings like 'get_mindmap' or 'get_selection', which might also retrieve mindmap data.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools such as 'get_mindmap' or 'get_selection', nor does it specify prerequisites like requiring an open mindmap. Usage is implied through the action of extraction, but no explicit context or exclusions are provided.

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/robertZaufall/mindm-mcp'

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