Skip to main content
Glama
marioluciofjr

MCP-Server de Mapas Mentais

by marioluciofjr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

apresenta

Generate mind maps for presentations on any topic to organize ideas visually and structure content effectively.

Instructions

Gera um mapa mental para apresentações sobre um tema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
temaYes

Implementation Reference

  • server.py:45-45 (registration)
    Registration of the 'apresenta' tool using the @mcp.tool decorator.
    @mcp.tool(name="apresenta")
  • server.py:46-55 (handler)
    The handler function for the 'apresenta' tool. It takes a theme string and returns a formatted string outlining presentation topics as a mind map structure.
    def apresenta(tema: str) -> str:
    """Gera um mapa mental para apresentações sobre um tema."""
    return (
        f"Apresentação sobre {tema}, focando somente nos tópicos abaixo:\n"
        f"- O que é\n"
        f"- Diferenças entre o {tema} e um conceito similar\n"
        f"- Exemplos de ferramentas\n"
        f"- Vantagens e desafios\n"
        f"- Casos de uso"
    )
  • server.py:46-46 (schema)
    Input schema defined by the function signature: tema: str (input theme), returns str (mind map text).
    def apresenta(tema: str) -> str:

Tool Definition Quality

C2.8/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 the full burden of behavioral disclosure. It states the tool generates a mind map but doesn't describe what format the output takes (e.g., text, image, structured data), whether it's a read-only or mutating operation, or any performance characteristics. For a generation tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is extremely concise - a single sentence that directly states the tool's function. There's no wasted language or unnecessary elaboration. It's appropriately sized for a simple tool with one parameter.

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 no annotations, no output schema, and minimal parameter documentation, the description is incomplete. It tells what the tool does at a high level but doesn't provide enough information about how to use it effectively, what to expect as output, or how it differs from sibling tools. For a generation tool, more context about output format and behavioral characteristics would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, and the tool description doesn't mention any parameters at all. While the parameter 'tema' (topic) is self-explanatory, the description provides no additional context about what constitutes a valid topic, format expectations, or examples. With low schema coverage, the description fails to compensate.

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: 'Gera um mapa mental para apresentações sobre um tema' (Generates a mind map for presentations on a topic). It specifies the verb ('gera' - generates) and resource ('mapa mental' - mind map) with the context of presentations. However, it doesn't differentiate from sibling tools like 'compara' or 'revisa' which might have related functions.

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 any prerequisites, exclusions, or suggest when to choose this over sibling tools like 'compara' or 'revisa'. The usage context is implied (for presentations on a topic) but lacks explicit when/when-not instructions.

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