Geode

Messaging: delete an open list

geode_messaging_delete_an_open_list

Destructive

Delete 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. Irreversible: the first call returns a confirm_token; call again with it to proceed.

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>",
      "delete_list_id": "<delete_list_id>"
    },
    "name": "geode_messaging_delete_an_open_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.
`confirm_token`	No	Token from the first call, to confirm this irreversible action
`delete_list_id`	Yes	0x-prefixed 32-byte hex id

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: it discloses that the operation writes to the chain, prepares an unsigned intent rather than executing directly, is irreversible, and requires a two-step confirm_token handshake. This is exactly the kind of behavioral detail the destructiveHint=true annotation does not convey.

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?

Three tight sentences, front-loaded with the action and followed by the critical execution model and the irreversibility/confirmation detail. No wasted text.

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 destructive, chain-writing tool with no output schema, the description covers ownership, execution model, required follow-up tools, irreversibility, and the confirm_token workflow. An agent has everything needed to call it correctly and safely.

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 three parameters are already documented, including signer address, delete_list_id format, and confirm_token purpose. The description reinforces the confirm_token flow but adds little format or semantic detail beyond the schema, warranting the baseline of 3.

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 ('Delete an open list') with an ownership qualifier ('you own'). It does not explicitly differentiate from nearby siblings like geode_messaging_leave_a_group or geode_messaging_join_an_open_list, but the resource name is unambiguous.

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 explains the workflow (sign with geode-local-signer, submit with geode_submit_intent) but does not state when to use this tool versus related destructive messaging tools such as delete_single_message_to_list or unsubscribe_from_open_list. Usage is implied by the ownership phrase 'you own'.

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?