Skip to main content
Glama
marioluciofjr

MCP-Server de Mapas Mentais

by marioluciofjr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

inicial

Generate a beginner-friendly mind map to visualize and organize foundational knowledge on any topic for clear understanding.

Instructions

Gera um mapa mental de conhecimentos iniciais sobre o tema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
temaYes

Implementation Reference

  • server.py:58-66 (handler)
    The handler function for the 'inicial' tool. It takes a 'tema' string parameter and returns a formatted string outlining initial knowledge topics (Remember, Understand, Apply) for generating a mental map.
    @mcp.tool(name="inicial")
def inicial(tema: str) -> str:
    """Gera um mapa mental de conhecimentos iniciais sobre o tema."""
    return (
        f"Conhecimentos iniciais sobre {tema}, focando somente nos tópicos abaixo:\n"
        f"- Lembrar: liste definições, fatos e informações básicas.\n"
        f"- Compreender: explique conceitos, forneça exemplos e traduza ideias.\n"
        f"- Aplicar: descreva como o conhecimento pode ser usado na prática."
    )
  • server.py:58-58 (registration)
    Registration of the 'inicial' tool using the @mcp.tool decorator with name 'inicial'.
    @mcp.tool(name="inicial")
  • server.py:59-59 (schema)
    Type schema for the 'inicial' tool: input 'tema' as str, output str.
    def inicial(tema: str) -> str:

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions generation but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, rate limits, or what format the mind map output takes. The description is minimal and lacks essential operational context.

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 a single, efficient sentence that directly states the tool's function. It's appropriately sized and front-loaded with the core action, though it could be more structured with additional context.

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

Completeness2/5

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

Given the tool's complexity (generating a mind map), lack of annotations, no output schema, and minimal parameter details, the description is incomplete. It doesn't explain what the output looks like, how the mind map is structured, or any limitations, leaving significant gaps for the agent.

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 0%, so the description must compensate. It implies the parameter 'tema' is the topic for the mind map, adding some meaning beyond the bare schema. However, with only one parameter, the baseline is 4, but the description doesn't fully detail the parameter's semantics (e.g., format, scope), so it scores slightly lower.

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

Purpose3/5

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

The description states the tool 'generates an initial knowledge mind map about the topic', which provides a clear verb ('generates') and resource ('mind map'). However, it doesn't specify what distinguishes this from sibling tools like 'apresenta' or 'revisa', leaving the purpose somewhat vague in context.

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 prerequisites, appropriate contexts, or exclusions, leaving the agent with no usage direction beyond the basic purpose.

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/marioluciofjr/mapas_mentais_mcp'

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