Skip to main content
Glama
Sign In

Wiggle

by io.github.jamesonhussey
OverviewDiscussionsAdmin

create_role

Create a room role with optional permissions (manage roles, create polls, invite). Requires can_manage_roles (the room creator has 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": {
      "room": "<room>",
      "name": "<name>"
    },
    "name": "create_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the role.
roomYesSlug of the room.
can_inviteNoGrant invite permission to holders.
can_create_pollsNoGrant poll-creation permission to holders.
can_manage_rolesNoGrant role-management permission to holders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / can_create_polls / description
      Added value: +"Grant poll-creation permission to holders."
    • addedInput schema / properties / can_invite / description
      Added value: +"Grant invite permission to holders."
    • addedInput schema / properties / can_manage_roles / description
      Added value: +"Grant role-management permission to holders."
    • addedInput schema / properties / name / description
      Added value: +"Name of the role."
    • addedInput schema / properties / room / description
      Added value: +"Slug of the room."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as a non-read, non-destructive action. The description adds a meaningful behavioral detail: the caller must hold can_manage_roles, and it clarifies that the room creator has this by default. It does not fully describe duplicate-handling or side effects, but the key operational constraint is covered.

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?

Two short sentences, front-loaded with the core purpose and permissions, followed by the required capability. Every sentence earns its place with no filler or redundancy.

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 creation tool with five simple parameters and no output schema, the description covers the essential context: what is created, what options exist, and who may do it. The main omission is not naming the alternative assign_role, but the tool can still be invoked correctly from the provided information.

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 coverage is 100%, so the schema fully describes all five parameters. The description adds a helpful summary of the optional permission flags, but it does not add meaning beyond what the schema already provides for room and name.

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 identifies the action ('Create') and resource ('a room role'), and names the optional permissions involved. It is unambiguous about what the tool does, though it does not explicitly contrast itself with the sibling assign_role.

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 description gives clear context for when to use the tool: when creating a role with optional permissions in a room. It also states the authorization prerequisite (can_manage_roles), but it does not mention when to prefer another tool such as assign_role instead.

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

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