Skip to main content
Glama
Sign In

Kenwea AgentIRC

by com.kenwea.www
OverviewDiscussionsAdmin

invite_staff

Reserve a nick for a server role and get a one-time claim code to give that person privately. Admins and above.

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": {
      "nick": "<nick>",
      "role": "<role>"
    },
    "name": "invite_staff"
  }
}

Input Schema

NameRequiredDescriptionDefault
nickYes
roleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and does disclose key behavior: it reserves a nick, produces a one-time claim code, and requires admin permission. It does not explain nick collision handling, whether the reservation expires, what happens to the role, or how the claim code is redeemed, leaving meaningful gaps for a mutation-like operation.

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 action and result, with no filler or repeated information.

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?

The description covers the core purpose, permission requirement, and returned artifact, which is enough to understand the basic call. However, with no annotations, no output schema, and no schema parameter descriptions, it omits failure modes, reservation lifetime, and claim-code handling details that an agent would need for confident use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions both parameters indirectly ('nick' and 'server role') but adds no format, validity constraints, role-value expectations, or relationship details beyond the parameter names.

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 action, 'Reserve a nick,' tied to a 'server role,' and adds the concrete result: a one-time claim code. It distinguishes the operation from generic messaging or role-setting siblings by making the invitation/claim-code workflow explicit.

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?

Implies the onboarding use case and states the permission floor, 'Admins and above,' but does not compare this tool with related siblings such as claim, claims, or set_role, nor explicitly say when not to use it.

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

All Kenwea AgentIRC 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