Geode

Messaging: find groups by keyword

geode_messaging_find_groups_by_keyword

Read-only

Search public messaging groups by up to three keywords. Read-only; no signature. Optional caller: the account whose view to read (for caller-dependent results).

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": {
      "keywords1": "<keywords1>",
      "keywords2": "<keywords2>",
      "keywords3": "<keywords3>"
    },
    "name": "geode_messaging_find_groups_by_keyword"
  }
}

Input Schema

Name	Required	Description
`caller`	No	Optional account address (SS58) to run the query as
`keywords1`	Yes	UTF-8 text, at most 512 bytes; no control or invisible characters
`keywords2`	Yes	UTF-8 text, at most 512 bytes; no control or invisible characters
`keywords3`	Yes	UTF-8 text, at most 512 bytes; no control or invisible characters

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds useful context beyond them: 'no signature' tells the agent no auth/signing is required, and it explains the caller-dependent view semantics. It stops short of describing result shape or pagination, but it clearly enriches the safety profile.

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 packed sentences with the core purpose front-loaded and no wasted wording. The read-only/signature note and the caller clarification both earn their place.

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?

For a read-only open-world search with no output schema, the description covers purpose, keyword constraints, auth expectations, and the caller parameter adequately. It could note result ordering or limits, but annotations and schema already carry most of the remaining load.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description goes slightly beyond the schema by clarifying the three keywords are 'up to three' and that caller is 'the account whose view to read (for caller-dependent results)', which adds intent the raw SS58 field description does not convey.

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 (search) and resource (public messaging groups) with the scope 'by up to three keywords'. It implicitly distinguishes itself from sibling geode_messaging_get_my_groups by scoping to 'public' groups, but it never names that sibling or the analogous find_lists_by_keyword, so differentiation is left to inference.

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?

Usage is implied by 'Search public messaging groups' – an agent can infer it is for discovery rather than management. However, there is no explicit when-to-use vs geode_messaging_get_my_groups or geode_messaging_find_lists_by_keyword, and no stated prerequisites or 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?