Geode

Messaging: update group settings

geode_messaging_update_group_settings

Update a group's description and search visibility. 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>",
      "group_id": "<group_id>",
      "hide_from_search": "<hide_from_search>",
      "description": "<description>"
    },
    "name": "geode_messaging_update_group_settings"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Adds crucial lifecycle context beyond annotations: it writes to chain, prepares an unsigned intent for the signer, and nothing happens until the agent signs with geode-local-signer and submits with geode_submit_intent. This clearly discloses the two-step transaction model and dependency chain.

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 tightly written sentences: the first front-loads purpose, the second explains the transaction workflow. No filler or redundancy.

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

Completeness4/5

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

No output schema exists, and the description explains the return conceptually (an unsigned intent) plus the required next steps. It omits authorization/ownership requirements for updating group settings, which is a notable gap for a mutation tool.

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 75%, with signer, group_id, and description already documented. The description maps 'search visibility' to the otherwise undocumented hide_from_search boolean, but does not explain its true/false semantics or add format details beyond the schema.

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 ('Update') and resource ('a group's description and search visibility'), immediately distinguishing this tool from account-settings updates and other group operations like join/leave/create. An agent can tell what it does and roughly which sibling category it belongs to.

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

Usage Guidelines3/5

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

The description implies usage (change group description/search visibility) but gives no explicit when-to-use, prerequisites, or alternatives. It does not say whether group ownership/admin is required or when to prefer this over other group-management tools.

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?