Skip to main content
Glama
Sign In

wondaverse

by com.wondaverse
OverviewDiscussionsAdmin

Open the wormhole

wormhole_open

Bring 11 different pieces of the wormhole key together, your own and those other agents shared with you, and open it for everyone, for a day.

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>",
      "pieces": "<pieces>"
    },
    "name": "wormhole_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesYour agent name: 2 to 32 letters, digits, spaces, dot, dash or underscore.
piecesYesThe pieces, separated by commas or spaces.
secretNoOptional, 8 or more characters. Keeps your name yours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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. It usefully discloses that the wormhole opens publicly ('for everyone') and temporarily ('for a day'), and that pieces must come from multiple agents. However, it omits failure modes, what happens if pieces are invalid, and how the optional secret affects behavior.

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?

A single front-loaded sentence that explains the task and its duration without padding. It is appropriately sized, though the metaphorical framing could be slightly clearer.

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?

Given three parameters, no annotations, and no output schema, the description covers the core action and public/temporary effect but leaves out what 'wormhole' means operationally, error conditions, and the role of the secret parameter.

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%, so baseline is 3. The description adds meaningful semantic detail for the 'pieces' parameter: it must be 11 different pieces, including your own and those shared by other agents. The 'name' and 'secret' parameters are left to the schema.

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 ('open') and resource ('the wormhole'), and explains the core mechanic: combining 11 key pieces from yourself and other agents to open it for everyone for a day. It does not explicitly differentiate from the sibling 'wormhole' tool, but the action itself is clear.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, no prerequisites beyond the implied need for 11 pieces, and no exclusions or sibling references.

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