Geode

Messaging: send message to list

geode_messaging_send_message_to_list

Broadcast a message to an open list you own. Writes to the chain: this prepares an unsigned transaction (an intent) for signer; nothing happens until you sign it with geode-local-signer and submit it with geode_submit_intent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "signer": "<signer>",
      "to_list_id": "<to_list_id>",
      "new_message": "<new_message>",
      "file_url": "<file_url>"
    },
    "name": "geode_messaging_send_message_to_list"
  }
}

Input Schema

Name	Required	Description
`signer`	Yes	Your account address (SS58). The transaction is prepared for this account; you sign it on your own machine with geode-local-signer.
`file_url`	Yes	https:// URL or empty string, at most 512 bytes
`to_list_id`	Yes	0x-prefixed 32-byte hex id
`new_message`	Yes	UTF-8 text, at most 2048 bytes; no control or invisible characters

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds crucial context the annotations cannot convey: this writes to the chain, but only prepares an unsigned intent, and nothing is committed until the user signs and submits. This two-step async pattern is exactly the behavioral detail an agent needs.

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?

Two sentences, no waste, and the core purpose and scope are front-loaded before the workflow caveat. Every clause earns its place.

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

Completeness5/5

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

For a chain-mutating tool with no output schema, the description supplies the missing pieces: the write semantics, the intent/unsigned-transaction model, and the required follow-up calls. An agent has everything needed to invoke it correctly.

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 all four parameters (signer, file_url, to_list_id, new_message) are already documented in the schema. The description only references `signer` in passing, adding no new format or constraint details beyond what the schema provides; baseline 3 is appropriate.

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?

States a specific verb ('Broadcast') and resource ('message to an open list you own'), with the ownership scope baked in. This clearly distinguishes it from send_message_to_group, send_private_message, and send_paid_message without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'open list you own' phrasing gives a clear precondition for use, and the sentence spells out the follow-up workflow (sign with geode-local-signer, submit with geode_submit_intent). It does not explicitly name when to prefer an alternative sibling, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Geode tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?