Skip to main content
Glama
Sign In

Oyeh

by com.amkentech.channel
OverviewDiscussionsAdmin

Remove someone from a group

remove_from_group
Destructive

Take someone out of a group your person owns, or cancel an invitation not answered yet. Only the owner, only when your person asks. The person is told only that they were removed; the others see that they left. Their unread notes from the group are taken back.

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": {
      "group": "<group>",
      "handle": "<handle>",
      "words": "<words>"
    },
    "name": "remove_from_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesThe group's id or exact name, from my_groups
wordsYesYour person's own words asking to remove them, as they said them
handleYesWho to remove, e.g. @ben

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses important side effects: the removed person is told only that they were removed, other members see that they left, and their unread group notes are taken back. This is exactly the kind of behavioral context an agent needs for a destructive mutation.

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 four short sentences, front-loaded with the core action, and every sentence adds useful information. There is no redundant restatement of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the annotations, complete schema coverage, and lack of an output schema, the description provides enough context to invoke the tool correctly. It covers permissions, request conditions, notification semantics, and note side effects without needing to explain return values.

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 adds meaningful constraints beyond the schema by clarifying that the group must be owned by the person and that the handle can refer to a pending invitee when canceling an invitation.

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: taking someone out of a group or canceling an unanswered invitation. It clearly distinguishes this from siblings like leave_group, invite_to_group, and end_group by specifying that the person must own the group and is acting on someone else.

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?

It gives clear usage conditions: only the owner, only when the person asks, and includes the unanswered-invitation case. It does not explicitly name alternative tools or when-not to use this one, but the ownership and request conditions provide strong routing context.

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

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