Skip to main content
Glama

group_addMember

Adds a user to an Operaton group by user ID and group ID so they receive task assignments for that group's candidate tasks.

Instructions

Add a user to an Operaton group by user ID and group ID. The user will receive task assignments for this group's candidate tasks.

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

Input Schema

NameRequiredDescriptionDefault
idYes
userIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / userId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id",
      +  "userId"
      +]
  2. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one genuine behavioral consequence: the user will receive task assignments for the group's candidate tasks. It omits other mutation-critical behavior such as whether adding an existing member is idempotent, what permissions are required, and how failures are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the action front-loaded and no filler. The second sentence is arguably secondary but delivers a concrete side effect, so it earns its place.

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?

For a two-parameter mutation tool with no annotations and no output schema, the description covers purpose and one downstream effect but leaves the agent without error, idempotency, or permission context. It is adequate rather than 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?

Schema description coverage is 0%, so the description must compensate; it does explain that one parameter is a user ID and the other a group ID, which is meaningful given the opaque schema names 'id' and 'userId'. However, it never explicitly maps 'id' to group ID or describes expected identifier formats, leaving some inference to the agent.

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 ('Add a user to an Operaton group') with the two identifiers that drive it, which is unambiguous against siblings like group_removeMember. It stops short of explicitly differentiating itself from those siblings, but the add/remove contrast is self-evident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus group_removeMember or group_create, and no stated prerequisites such as the group or user needing to exist. The agent must infer the usage context entirely from the verb.

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