Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

Configure a rig sub-page on your page

page_rig_config

Owner config for ONE of your published rigs on your page: showcase (SHOW this rig on your public profile + give it a config card — opt-in; publishing alone no longer showcases a rig), mode ('builder' rig-detail view or 'app' app-output surface), featured (headline it in your SHOWCASE — single slot, featuring one un-features the rest), linked (mint the public /@handle/ link — rigs do NOT get sub-pages unless you opt in), plus the sub-page's PRODUCT theme: tagline (≤140 chars under the rig name), accent (#rrggbb page accent color), glyph (an emoji/1-2 char hero mark). Pass an empty string to clear a theme field. Claim your page first. Requires Authorization: Bearer .

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
slugYesthe rig's slug (lowercase alnum + dashes — derived from its name)
glyphNohero glyph — an emoji or 1-2 chars ('' clears)
accentNopage accent color as #rrggbb ('' clears)
linkedNo
galleryNoup to 6 https image URLs for the page's MEDIA panel (screenshots, brand art; [] clears)
taglineNoproduct tagline shown under the rig name (≤140 chars; '' clears)
featuredNo
residentNoPRO: keep an always-on sandbox behind this page — instant live dashboard + warm interactions; owner-metered; fail-closed on tier lapse
showcaseNoshow this rig on your public profile (and give it a config card) — opt-in; false hides it
banner_urlNohero banner image — an https URL (the product's brand backdrop + share-card image; '' clears)
hero_imageNohero PICTURE — a small data:image/... URI (≤260k chars; a 256px square, profile-photo style) replacing the glyph ('' clears)
hide_inputNohide the RUN IT input field — the button fires with resident_input (the default input) or empty
capabilitiesNoup to 8 short bullets (≤120 chars) — 'what this rig does', the page's get-to-the-point card ([] clears; the page then derives bullets from the pipeline)
pin_showcaseNofreeze (true) / unfreeze (false) the current showcase snapshot
stage_staticNoSTATIC stage — the main area shows the cached showcase only (no run panel, no in-dashboard actions); a portfolio piece rather than a live app
auto_showcaseNoauto-refresh the page's public showcase from YOUR successful runs of this rig (visitors always see the latest dashboard; their runs never touch it)
clear_showcaseNodelete the stored showcase snapshot
resident_inputNothe resident's default input for boot/periodic refreshes, e.g. a token address ('' clears)
resident_interval_secsNoperiodic self-refresh cadence in seconds (min 300; 0 clears)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only provide readOnlyHint=false and destructiveHint=false, leaving the description to carry behavioral details. It adds significant context: opt-in behavior for showcase and linked, clearing theme fields with empty strings, the single-slot rule for featured, and authentication requirements. This goes well beyond the minimal annotations.

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 long but well-structured, front-loading the purpose and then grouping related options. Each clause is meaningful and contributes to understanding the tool. It could be slightly more concise, but the complexity of 20 parameters justifies the length.

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 complex tool with no output schema, the description covers prerequisites, authentication, main behavioral semantics, and how to clear fields. It does not mention the return value or error conditions, but these are less critical for a configuration mutation. The main gap is the lack of explicit sibling differentiation, which is more of a usage guideline issue.

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?

The schema has 85% coverage with many parameter descriptions, but some key parameters (mode, featured, linked) lack schema descriptions. The description adds meaning for these, clarifying mode values, featured's single-slot rule, and linked's opt-in link minting. This adds value beyond the schema, though not for all 20 parameters.

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 clearly states it configures a rig sub-page for a published rig, listing specific aspects like showcase, mode, featured, linked, and theme fields. It is specific about the resource and action, but does not explicitly differentiate from sibling page_* or rig_* tools, so it misses the full 5.

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 provides clear context including prerequisites ('Claim your page first') and authentication requirements, and explains the opt-in nature of some features. However, it does not explicitly state when to use this tool versus alternatives (e.g., page_claim or rig_stage_set), so it lacks exclusions.

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

All Rokha 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