Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Search public Worlds by name

imagine_search_public_worlds
Read-onlyIdempotent

Find public Worlds by name, to add a Character to or to choose when building a Character with vault_build_pc. Returns up to 20 public, active Worlds whose name contains the text, by name, each { _id, name, summary, image, link }. Worlds the caller owns or holds a role on are left out (imagine_list_my_worlds lists those). Fewer than two characters of text returns an empty list.

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": {
      "query": "<query>"
    },
    "name": "imagine_search_public_worlds"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesText to find in a World's name, case-insensitive. Fewer than two characters finds nothing.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the 20-item cap, the name-substring match semantics, the silent exclusion of owned and role-holding Worlds, and the empty-result behavior for short queries. That is exactly the behavior an agent cannot infer from annotations or schema.

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?

Four tight sentences: purpose, use case, return contract, exclusion rule, edge case. No filler, and the most decision-relevant information (public-only, name match) is front-loaded.

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 single-parameter search tool with an output schema, it covers everything an agent needs: what matches, what is omitted, how many results, and what the return fields are. No significant gap remains for correct invocation.

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 coverage is 100%, so the baseline is 3; the description adds value by stating the two-character effective minimum and case-insensitive substring matching against name, which goes beyond the schema's minLength of 1. It doesn't describe quoting or special-character handling, so it falls short of a 5.

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 and resource (find public Worlds by name) plus the exact matching rule (name contains the text), the result cap (up to 20), and the returned shape `{ _id, name, summary, image, link }`. It also distinguishes itself from imagine_list_my_worlds, so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use contexts (adding a Character to a World, or selecting one via vault_build_pc) and an explicit exclusion rule with the sibling that covers that case (owned/role Worlds → imagine_list_my_worlds). The minimum-input behavior (fewer than two characters returns an empty list) tells the agent when the call is wasted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources