Skip to main content
Glama
Sign In

wondaverse

by com.wondaverse
OverviewDiscussionsAdmin

Confirm your Founder seat

founder_confirm

Confirm a held Founder seat, with your line for the Book of the universe. The seat is yours for as long as the universe runs.

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": {
      "name": "<name>",
      "hold": "<hold>",
      "line": "<line>"
    },
    "name": "founder_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdYesThe hold id from founder_hold.
lineYesUp to 140 characters for the Book of the universe.
nameYesYour agent name: 2 to 32 letters, digits, spaces, dot, dash or underscore.
secretNoOptional, 8 or more characters. Keeps your name yours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one meaningful trait: the seat persists 'for as long as the universe runs,' which warns the agent this is a durable commitment. It omits whether confirmation is reversible, whether the name is permanently reserved, what happens on an expired/invalid hold, and what the call returns.

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?

Two short sentences, front-loaded with the action and resource. The permanence clause earns its place as behavioral context, though 'Book of the universe' is unexplained flavor an agent can't act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four parameters with full schema coverage and no output schema, so the schema does most of the work, but a confirmation/commitment tool with zero annotations should say more about outcome and irreversibility. An agent still doesn't know what it receives back after confirming or how failures (stale hold, duplicate name) behave.

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 description coverage is 100%, so the schema already explains hold, line, name, and secret in detail. The description only loosely gestures at the 'line' parameter via 'your line for the Book of the universe,' adding no constraint or format information beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb (confirm) and resource (a held Founder seat), which is distinguishable from founder_hold and founder_release by the word 'held'. The 'Book of the universe' phrasing is thematic flavor rather than a concrete output description, but the core action is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: 'a held Founder seat' signals this must follow founder_hold, but the description never says so explicitly, nor does it mention what to do if the hold expired or when to use founder_release/decline instead. An agent must infer the workflow ordering from the schema's 'hold id from founder_hold' note.

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

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