Skip to main content
Glama
receptron

mulmocast-vision

Official
by receptron

createCommunicationPlanSlide

Create a communication plan matrix slide by specifying target audiences, channels, and optional cadence for presentations.

Instructions

Create or update a communication plan matrix.

Input Schema

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

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

No annotations are present, so the description must disclose all behavioral traits. It only says 'Create or update', implying mutation, but doesn't detail effects on existing slides, required permissions, reversibility, or side effects.

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, which is concise and front-loads the purpose. However, it sacrifices necessary detail, making it minimally acceptable.

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 4 parameters, no output schema, and no annotations, the description is too sparse. It fails to specify return values, formatting, or integration with other slides, leaving the agent with incomplete information.

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?

Schema description coverage is 25% (only _index has a description). The tool description does not explain any parameters beyond the schema. For example, 'cadence' is left undefined, and 'audiences'/'channels' lack semantic context.

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 creates or updates a communication plan matrix, which is a specific slide type. It uses a clear verb and resource, distinguishing it from other slide creation tools by specifying the content type.

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 is provided on when to use this tool versus sibling slide creation tools. The description does not mention context, prerequisites, or alternatives, leaving the agent without decision support.

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