Skip to main content
Glama

Coline

Set priority people

set_priority_people
DestructiveIdempotent

Replaces the people whose messages reach the person even during do not disturb.

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": {
      "workspace": "<workspace>",
      "contacts": "<contacts>"
    },
    "name": "set_priority_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactsYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered structurally. The description reinforces the destructive semantics by saying the list is "replaced," and clarifies the DND-bypass meaning, but it never states that existing priority people are discarded if omitted, nor what permissions are required.

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 or redundancy. It is efficient, though the brevity comes at the cost of the operational detail noted in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent-looking mutation the annotations carry the risk profile and an output schema exists, so return values need not be described. What remains missing is parameter-level meaning for the contacts array rather than general behavior, which is better attributed to parameter semantics than to overall completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: the workspace slug is documented in the schema, but the contacts array and its bypassDnd, contactUserId, and escalateAfterMinutes fields carry no descriptions anywhere. The description does not compensate at all, leaving the escalation-time semantics (1–1440 minutes) and the 50-contact cap completely unexplained.

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?

The description uses a specific verb ("Replaces") and a clearly delimited resource (the set of people whose messages bypass do-not-disturb), which maps directly to the tool name. It is understandable without opening the schema, though it does not explicitly contrast itself with siblings like set_message_priority or set_notification_keywords.

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 when-to-use or when-not-to-use guidance and no named alternative; an agent is not told, for example, to use find_people to obtain contactUserId values first. The only implicit guidance is the word "Replaces," which hints at full-list overwrite semantics but is never stated as an operational rule.

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