Skip to main content
Glama

get_inbox_assignment

Read-onlyIdempotent

Read the assigned team member ID for a contact's Inbox conversation in the approved business.

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

Input Schema

NameRequiredDescriptionDefault
contactIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful scoping (contact's Inbox conversation, approved business) and states the return is a team member ID, but it does not say what happens when no one is assigned (null, empty, or error).

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?

A single front-loaded sentence with no filler; the resource and scope come before any qualifications. It is arguably under-specified rather than bloated, so it earns its length but could carry one more clause about the unassigned case.

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 one-parameter read there is no output schema, so the description is the only source of return-value information, and it only says a team member ID comes back. The absent-assignment case, the biggest thing an agent must handle, is left unstated.

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?

With a single parameter and 0% schema description coverage, the schema names contactId but explains nothing; the description compensates partially by tying it to "a contact's Inbox conversation." It does not address the accepted ID format or how an invalid/unknown contact is handled.

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?

States a specific verb ("Read") and a specific resource ("the assigned team member ID"), scoped to a contact's Inbox conversation. This implicitly contrasts with the write sibling set_inbox_assignment, though it never names an alternative 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?

Usage is only implied: an agent can infer this is the read counterpart used when it needs to know who is currently assigned. There is no explicit when-to-use statement, no mention of prerequisites such as the contact needing an existing Inbox conversation, and no named alternative.

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