Skip to main content
Glama

set_inbox_assignment

Idempotent

Assign a contact's Inbox conversation to a business team member, or pass null to clear it. Use list_pipeline_assignees to find member IDs.

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": {
      "contactId": "<contactId>",
      "assigneeId": "<assigneeId>"
    },
    "name": "set_inbox_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactIdYes
assigneeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare this is a non-read-only, idempotent, non-destructive mutation, so the description need not repeat that. It adds meaningful behavior beyond annotations by explaining that passing null clears the assignment, which is not evident from the schema alone. It does not describe the response or permission requirements, keeping it short of a 5.

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 tight sentences with the primary action and null behavior front-loaded, followed by the ID-lookup instruction. No redundant or filler wording.

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 covering safety and idempotency and no output schema, the description covers the core action, the clearing case, and where to obtain assignee IDs. Minor gaps remain around contactId expectations and permissions, but nothing essential for correct invocation is missing.

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 carry parameter meaning. It explains assigneeId's null-clearing behavior and points to list_pipeline_assignees for valid IDs, but contactId is only implied by 'a contact's Inbox conversation' and its format constraints are left entirely to the schema.

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: assigning a contact's Inbox conversation to a business team member, with the null case for clearing. This distinguishes it clearly from the sibling read tool get_inbox_assignment and from the assignee-listing tool.

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 explicitly tells the agent to use list_pipeline_assignees to find member IDs, which is actionable routing guidance. It also clarifies the null case, though it does not state exclusions or prerequisites such as required permissions.

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