Skip to main content
Glama
Sign In

Embers: Tabletop RPG Toolkit

by com.embersds
OverviewDiscussionsAdmin

List pages authored by a user

play_list_user_pages
Read-onlyIdempotent

List the pages a given user has authored. Pass own user id (from whoami) to see private pages too; for another user, only their public pages that the caller may read come back (pages of campaigns the caller may view, or with no ref). Defaults to summary shape.

Input Schema

NameRequiredDescriptionDefault
detailNoResponse shape. 'summary' (default) drops the markdown `description` body and trims the owner populate, keeping identification + `ref` + `documentType` + the short `summary` field. 'full' returns the populated page document including the full body.summary
userIdYesMongo `_id` of the user whose pages to list. Pass own user id (from `whoami`) to see private pages too; for another user, only their public pages that the caller may read come back (pages of campaigns the caller may view, or with no ref).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userId / description
      Previous value: -"Mongo `_id` of the user whose pages to list. Pass own user id (from `whoami`) to see private pages too; for another user, only public pages come back."New value: +"Mongo `_id` of the user whose pages to list. Pass own user id (from `whoami`) to see private pages too; for another user, only their public pages that the caller may read come back (pages of campaigns the caller may view, or with no ref)."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive operation. The description adds important context about privacy filtering and the default response shape, which goes beyond annotations. It does not discuss pagination or error behavior, but the annotations lower the bar.

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 tight sentences with zero waste. The privacy behavior is front-loaded right after the core action.

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?

Given a simple two-parameter read operation with an output schema and annotations, the description covers the essential access-control nuance and default shape. Pagination is not mentioned, but that is a minor gap.

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 coverage is 100%, so both parameters are documented in the schema. The description repeats the semantics of userId and mentions the default detail shape, but adds little beyond what the schema provides.

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 ('List'), resource ('pages'), and scope constraint ('authored by a given user'). Clear enough that an agent can distinguish it from siblings like play_list_pages or imagine_list_adventure_pages.

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?

Explains a key usage distinction: passing your own user id (from whoami) reveals private pages, while another user's id yields only public pages readable by the caller. It doesn't explicitly name alternative list tools, but the context is clear enough to guide usage.

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

All Embers: Tabletop RPG Toolkit toolsInspect
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