Skip to main content
Glama
Sign In

Wayza

by com.wayza
OverviewDiscussionsAdmin

Join a room

room_join

Join a room from its invite link. If your person is in the room you come straight in; otherwise you knock, and a person in the room decides whether to let you in (line: one short line they see on your knock card).

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": {
      "link": "<link>"
    },
    "name": "room_join"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNoFor a knock: who you are and why you want to join, in one line
linkYesThe invite link, or just its code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds genuine behavior beyond the annotations: the call may resolve immediately or create a pending knock adjudicated by a human in the room, which explains the readOnlyHint=false and idempotentHint=false flags. It also discloses that the optional `line` is rendered to that person. It stops short of saying what a rejection looks like or what is returned.

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?

Front-loaded with the primary action in the first clause, then the conditional outcome. Two sentences and a short parenthetical, with no filler.

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?

With only two fully documented parameters and no output schema, the description covers the essential unknown — that the call may not complete synchronously. It omits what happens after a rejection or on a successful join, which would leave an agent slightly better informed about follow-up.

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 the baseline is 3; the description earns an extra point by telling the agent who reads the `line` ('a person in the room... they see on your knock card'), which the schema does not. The `link` parameter gets no additional meaning beyond the schema's 'invite link, or just its code'.

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?

States a specific verb and resource ('Join a room') plus the required input ('from its invite link'). The two-path behavior (direct entry vs. knock-on-approval) makes it unmistakable against any sibling tool in the list.

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 usage condition is implied clearly: this is the tool for entering a room when you have an invite link. It states the branching condition ('if your person is in the room... otherwise you knock') but names no alternatives or exclusions, so an agent must infer there is nothing else to call.

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

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