Skip to main content
Glama
Cyoda-platform

Cyoda Calculation Node MCP

Official

edge_message_send_edge_message_tool

Send an edge message to the Cyoda platform by providing a subject and content, with optional fields for message ID, recipient, and correlation ID.

Instructions

Send a new edge message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesMessage subject
contentYesMessage content as dictionary
message_idNoOptional message ID
user_idNoOptional user ID
recipientNoOptional recipient
reply_toNoOptional reply-to address
correlation_idNoOptional correlation ID
content_encodingNoOptional content encoding
content_lengthNoOptional content length
content_typeNoContent type (default: application/json)application/json

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, and the description only says 'send', implying mutation, but lacks details on success behavior, authentication, or limits.

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 with no wasted words, though it is brief.

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 10 parameters and an output schema, the one-sentence description is insufficient; it lacks context about the messaging system and return values.

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 100%, so the schema already documents parameters; the tool description adds no additional meaning beyond that.

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

Purpose5/5

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

The description clearly states the action 'send' and the resource 'edge message', distinguishing it from the sibling get tool.

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 alternatives, nor any exclusions or prerequisites.

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/Cyoda-platform/mcp-cyoda-quart-app'

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