Skip to main content
Glama
Sign In
wiseoldman-mcp

wiseoldman-mcp

by jhaenen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Remove group members

wom_remove_group_members

Remove one or more members from a Wise Old Man group by providing their usernames and the group's verification code.

Instructions

Removes one or more members from a group by username. Requires the group's verification code.

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": {
      "id": "<id>",
      "verificationCode": "<verificationCode>",
      "usernames": "<usernames>"
    },
    "name": "wom_remove_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe group's numeric Wise Old Man ID.
usernamesYesUsernames to remove.
verificationCodeYesThe group's verification code, given when the group was created. Required for any mutating action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It discloses that the tool is a mutating action requiring a verification code, but does not mention any side effects, limits, or reversibility. This is adequate but minimal.

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 two sentences long with no wasted words. Every sentence adds value, and the key information is front-loaded.

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 simple tool with 3 required parameters and no output schema, the description covers the essential operational context. It could be improved by noting what happens on success or error, but the given information is sufficient for basic usage.

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?

The schema covers 100% of parameters with clear descriptions. The description adds no additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states the verb 'removes' and the resource 'members from a group by username', which distinguishes it from sibling tools like wom_add_group_members or wom_change_group_member_role.

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?

The description mentions the requirement for a verification code but does not provide explicit guidance on when to use or not use this tool versus alternatives. No exclusion criteria or alternative tool references are given.

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

Deploy Server

Other Tools