Skip to main content
Glama
Sign In
wiseoldman-mcp

wiseoldman-mcp

by jhaenen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update all outdated group members

wom_update_all_group_members

Queues an update for every outdated member in a group. Requires the group's ID and verification code.

Instructions

Queues an update/refresh for every outdated member in the group. Requires the group's verification code. Avoid calling this too frequently for the same group.

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>"
    },
    "name": "wom_update_all_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe group's numeric Wise Old Man ID.
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.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It mentions queuing an update (suggesting async behavior) and requires a verification code, but does not disclose what happens to non-outdated members, the exact effect, or any return value. Adequate but not thorough.

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 with no filler. All information is essential and front-loaded. Highly concise.

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?

Given no output schema and no annotations, the description is minimal. It explains the action and a key requirement but lacks details on what 'outdated' means, the queue behavior, rate limits, or error cases. Adequate for a simple tool but could be more complete.

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?

Both parameters have 100% schema coverage with descriptions. The description reinforces that verificationCode is required, but adds no new semantic meaning beyond what the schema already provides for id. Baseline 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 action: 'queues an update/refresh for every outdated member in the group.' It uses a specific verb (update/refresh) and resource (outdated members), distinguishing it from sibling tools like add or remove members.

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?

Explicitly requires the group's verification code and warns against calling too frequently. While it does not list alternatives or specify exact when-to-use vs other member tools, the caution and requirement provide usable context.

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