Skip to main content
Glama

Update Agents in Inbox

update_agents_in_inbox
Destructive

Update Agents in Inbox. Set the inbox's members to exactly the agents in user_ids: agents not in the list are removed from the inbox, new ones are added.

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": {
      "inbox_id": "<inbox_id>",
      "user_ids": "<user_ids>"
    },
    "name": "update_agents_in_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesThe ID of the inbox
user_idsYesIDs of users to be added to the inbox

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the destructiveHint=true annotation by spelling out precisely what is destroyed: agents absent from user_ids are removed, and new ones are added. That concrete consequence is more useful than the boolean hint. Minor tension: the described full-state replacement is naturally idempotent, yet idempotentHint=false is declared — not a contradiction of what the tool does, but worth noting; no auth or error behavior is described.

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 sentences, front-loaded with the operation and followed by the exact consequence. Nothing redundant; every clause adds information.

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 two-parameter mutation with annotations and no output schema, the definition covers the critical replacement semantics and the removal side effect. It does not state what is returned, how invalid or non-agent user IDs are handled, or required permissions, which leaves modest gaps for a destructive operation.

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%, but the schema's own wording for user_ids ("IDs of users to be added") is narrower than the actual semantics. The description corrects this by stating the array is the complete target membership set, which is essential meaning the schema alone would have gotten wrong.

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 ("Update Agents in Inbox") and immediately defines the operation as a full replacement: "Set the inbox's members to exactly the agents in user_ids." That removes ambiguity with sibling mutation tools like add_inbox_member/remove_inbox_member, though it never names those siblings explicitly.

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 'set exactly' phrasing implies this is the bulk/replace path rather than the incremental add/remove path, but no explicit when-to-use or when-not-to-use guidance is given. An agent must infer that add_inbox_member or remove_inbox_member is the right call for single-agent changes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources