Skip to main content
Glama
Sign In

Kenwea AgentIRC

by com.kenwea.www
OverviewDiscussionsAdmin

claim

Claim paths you are about to edit in a channel (your project's room), as a lease. Refused, with nothing claimed, if any path is the same as, inside or above a path another nick holds; the refusal names the holder and the expiry. A glob segment claims its directory. Claiming a path you already hold renews it. Release when done.

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": {
      "paths": "<paths>"
    },
    "name": "claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat you are doing, shown to anyone refused.
pathsYesProject-relative paths or directories, e.g. ["server/auth", "README.md"].
channelNoChannel, e.g. #general (the default).
ttl_minutesNoHow long the claim lasts (default 30).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 so well: it discloses atomic refusal ("nothing claimed"), the exact collision rule (same, inside or above another nick's path), that the refusal names the holder and expiry, that a glob segment claims its directory, and that re-claiming renews. It omits what a successful claim returns and any visibility of claims to other agents, which would round out the behavioral picture.

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?

Four tight sentences, front-loaded with purpose, then collision behavior, then renewal, then release. Every clause carries information; there is no filler or restatement of the title.

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 mutating coordination tool with no annotations and no output schema, the description covers the failure modes, renewal, and cleanup an agent needs to use it correctly. What remains missing is the success-side behavior (what the lease id or response looks like) and how claims are inspected by others.

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, and the description adds real meaning beyond the schema: "A glob segment claims its directory" defines how paths entries are interpreted, which the schema example (["server/auth", "README.md"]) does not convey. The ttl/expiry framing also reinforces ttl_minutes, though the note and channel parameters add nothing beyond their schema text.

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?

Names a specific verb and resource ("Claim paths ... as a lease") plus the scope (paths about to be edited, in a channel/project room). The lease framing separates it from a mere lock or a status read, and "Release when done" gestures at the release sibling. It stops short of naming the sibling that lists existing claims, so an agent must infer that distinction.

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?

"Claim paths you are about to edit" gives a clear trigger, and the lifecycle rules (re-claiming renews, "Release when done") tell the agent how to maintain and end a claim. No explicit when-not-to-claim rule or named alternative tool is given, which keeps it below a 5.

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