Geode

Messaging: send message to group

geode_messaging_send_message_to_group

Send a message to a group you belong to. 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_group_id": "<to_group_id>",
      "new_message": "<new_message>",
      "file_url": "<file_url>"
    },
    "name": "geode_messaging_send_message_to_group"
  }
}

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
`new_message`	Yes	UTF-8 text, at most 2048 bytes; no control or invisible characters
`to_group_id`	Yes	0x-prefixed 32-byte hex id

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing that this writes to the chain, produces an unsigned transaction (an intent), and has no effect until signed locally and submitted. This is exactly the kind of behavioral trait an agent needs to sequence correctly and is not derivable from the annotations alone.

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 tight sentences. The core action and group scope are front-loaded, and the second sentence carries the transaction-lifecycle detail with no filler.

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-writing tool with no output schema, the description covers the essential transaction lifecycle and gates the agent's next steps. Safety profile is handled by annotations and params are fully documented in the schema, so nothing critical is missing.

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% and all four parameters are documented, so the baseline is 3. The description mentions `signer` and its local-signing role, but the schema's own signer description already says the same thing, so the description adds little parameter meaning beyond structured data.

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?

States a specific verb and resource: 'Send a message to a group you belong to.' The scope ('a group you belong to') makes it distinguishable in practice from group-adjacent siblings. It does not explicitly name alternatives like geode_messaging_send_private_message or geode_messaging_send_message_to_list, so the differentiation is implicit rather than stated.

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?

Gives clear operational context: this only prepares an unsigned intent, and 'nothing happens until you sign it with geode-local-signer and submit it with geode_submit_intent.' That routes the agent through the correct two-step follow-up. It stops short of stating when to choose this over other messaging tools, so no explicit exclusions.

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?