Skip to main content
Glama
Sign In

Random Tables

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Roll Custom Table

roll_custom_table
Read-onlyIdempotent

Pipeworx original random tables: roll one or more entries from a table YOU supply — bring your own weighted list of { text, weight? } and get back a reproducible weighted draw. Entries may contain {{table:}} references to Pipeworx's BUILT-IN random tables (e.g. "{{table:npc_personality}}"), resolved recursively (up to 6 levels deep). Optional seed makes the roll reproducible; the seed used is always returned. No session support for custom tables — use roll_table for session-tracked built-in tables.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "seed": "pw-smoke-2",
      "count": 3,
      "entries": [
        {
          "text": "a {{table:npc_occupation}} with a grudge"
        },
        {
          "text": "an ordinary traveler",
          "weight": 2
        }
      ]
    },
    "name": "roll_custom_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoOptional seed for a reproducible roll. Omit for fresh randomness; the seed actually used is always returned.
countNoHow many entries to roll, 1-20 (default 1).
entriesYesYour table: a non-empty array of { text: string, weight?: number > 0 (default 1) }. Up to 500 entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context beyond annotations: recursive resolution up to 6 levels, reproducible seeded rolls, and the fact that the used seed is always returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and information-dense, with no wasted sentences. It is somewhat long due to the reference-resolution and session-support caveats, but every clause contributes relevant selection or invocation context.

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 three-parameter custom-table tool with full schema coverage and annotations, the description covers purpose, usage routing, seed reproducibility, recursive references, and session limitations. No output schema exists, and the description still notes the seed return behavior, so an agent has enough to invoke it correctly.

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 still adds meaning beyond the schema by explaining weighted draw semantics, recursive {{table:<id>}} resolution up to 6 levels, and that the seed used is returned.

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?

The description states a specific verb and resource: roll one or more entries from a user-supplied weighted table. It explicitly distinguishes this from roll_table by noting the lack of session support for custom tables, so an agent can route between them without opening both schemas.

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?

It names the alternative roll_table and gives the condition that selects it: session-tracked built-in tables. It also says there is no session support for custom tables, which is clear when-not guidance.

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

All Random Tables 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