Skip to main content
Glama

Embers: Tabletop RPG Toolkit

List campaigns a new Character can join

play_list_joinable_campaigns
Read-onlyIdempotent

List the campaigns a new Character of the given ruleset can join, as the app decides it: a bare array [{ _id, name }]. These are the campaigns to offer when building a Character with vault_get_pc_creation_options / vault_build_pc (campaignIds). A ruleset this account may not use returns an empty list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "play_list_joinable_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesetNoRuleset code of the new Character, from list_rulesets. Required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety story is covered. The description adds real behavioral detail beyond that: a bare array of `{_id, name}` and the empty-result case for a ruleset the account may not use.

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 sentences, front-loaded with purpose, then usage, then the edge case. No filler and nothing repeated from annotations or the schema verbatim.

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 single-parameter read tool with an output schema and full annotations, the description covers purpose, downstream use, and the notable empty-list edge case. The only minor gap is that 'as the app decides it' hints at opaque server-side filtering that is never explained.

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% and the schema already documents `ruleset` as coming from list_rulesets. The description still adds meaning by tying the parameter to a new Character's ruleset and by disclosing that an unusable ruleset yields an empty list rather than an error.

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?

The description opens with a specific verb and resource ('List the campaigns') and narrows the scope to 'a new Character of the given ruleset can join,' which conceptually separates it from the broader play_list_my_campaigns. It stops short of naming an alternative sibling outright, so an agent must infer the contrast rather than read it.

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?

It states the concrete use case: offer these campaigns when building a Character via vault_get_pc_creation_options / vault_build_pc, passing the ids as `campaignIds`. That is clear routing guidance with named consumers, though there is no explicit 'do not use this when...' branch.

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