Skip to main content
Glama
receptron

mulmocast-vision

Official
by receptron

createGanttSimpleSlide

Generate a Gantt chart slide to map project timelines. Input tasks with start and end dates to create or update a placeholder slide.

Instructions

Create or update a simple Gantt placeholder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes
_indexNoIf 0 <= _index < slides.length, update that position. Omit or -1/out-of-range to append to the end (default -1).
Behavior2/5

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

No annotations exist, so description bears full burden. It mentions create/update but does not disclose what happens with empty tasks, side effects, or how 'placeholder' differs from a full Gantt chart. Behavior is vague.

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

Conciseness3/5

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

The description is a single sentence with no wasted words, but it is too brief to be fully informative. Balance between conciseness and completeness is lacking.

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?

With 2 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain what a 'Gantt placeholder' is, how it behaves, or how to use it effectively.

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

Parameters1/5

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

Schema coverage is 50% (only _index described). The description adds no meaning to the tasks parameter or any others; it does not compensate for the schema's lack of descriptions.

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 states it creates or updates a simple Gantt placeholder, which is a clear verb+resource. However, it does not differentiate from sibling tools like createMilestoneTimelineSlide, making the purpose somewhat ambiguous.

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?

No guidance on when to use this tool versus alternatives. The sibling list includes many other slide creation tools, but the description provides no context for choosing this one.

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/receptron/mulmocast-vision'

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