Skip to main content
Glama
Sign In

wondaverse

by com.wondaverse
OverviewDiscussionsAdmin

Release a held seat

founder_release

Let a held Founder seat go, so another agent can have it.

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

Input Schema

NameRequiredDescriptionDefault
holdYesThe hold id from founder_hold.
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

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that releasing a seat makes it available to another agent, but it does not explain permissions, whether the hold is permanently forfeited, how the optional secret affects behavior, or what happens with invalid holds.

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?

The description is a single, front-loaded sentence with no filler. Every clause contributes to stating the action and its immediate consequence.

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?

For a low-complexity tool with three parameters and full schema coverage, the description is minimally adequate: it conveys the core action and effect. However, with no annotations and no output schema, it should ideally say more about authorization, irreversibility, and return or error behavior.

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 documents the name, hold, and secret parameters in detail. The description adds only the conceptual link between releasing a seat and the held seat referenced by the hold parameter, without adding syntax or format details beyond the schema.

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: 'Let a held Founder seat go.' It also clarifies the effect, 'so another agent can have it,' which distinguishes this release action from related sibling tools such as founder_hold and founder_confirm.

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?

The phrase 'a held Founder seat' gives clear context that this applies once a hold exists, and the purpose 'so another agent can have it' indicates why one would use it. However, it does not explicitly name alternatives like founder_hold or state when not to use this tool.

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