Skip to main content
Glama

Set Assignment Configuration

set_assignment_config
Destructive

Replace the WHOLE ownership routing configuration for one object: which field decides who owns a record, and for each value that field can hold, the pool of people it routes to and how one of them is picked. THIS IS A REPLACE, NOT A MERGE -- read the current configuration with get_assignment_config and send it back with your change, because any pool you omit is deleted. A pool matched by an unchanged value keeps its rotation position, so adding one person does not rewind the rotation for everyone else. field must be one of this connection's filterable fields (call list_filterable_fields) and every rep must be an ACTIVE user on this connection (call list_crm_users). Configuring a value no record currently holds is allowed -- a territory can be set up before anyone is in it. This writes nothing to the CRM and assigns nobody: it decides what a future assignment run would do.

Input Schema

NameRequiredDescriptionDefault
fieldYesThe field whose value decides the pool, e.g. billing_state. Call list_filterable_fields for this connection's fields.
poolsYesOne entry per value of that field you want routed. A value with no entry here is SKIPPED by a run, not assigned to anyone, unless a pool has the value "*": it takes every value no other pool does, empty ones included, so one "*" pool routes every record. Sending an empty list clears the configuration.
object_typeYesWhich object's ownership routing to configure.
connection_idYesThe CRM connection. Call list_crm_connections first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, and the description earns its credit by explaining exactly what is destroyed: omitted pools are deleted ('THIS IS A REPLACE, NOT A MERGE'). It adds rotation-position preservation on unchanged values and clarifies the tool writes nothing to the CRM and assigns nobody, which is critical non-obvious behavior beyond the annotations.

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?

Front-loaded with the highest-stakes fact (REPLACE, not merge) and every subsequent sentence is load-bearing: rotation preservation, field/user constraints, wildcard semantics, empty-list clearing. No filler or restatement of the name.

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?

A destructive, config-heavy mutation with no output schema, and the description covers the replace semantics, the cross-tool read-modify-write workflow, validation constraints, and side-effect profile. Nothing an agent needs to call it safely is missing.

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%, so the baseline is 3, but the description adds real meaning: field must be a filterable field of the connection, reps must be ACTIVE CRM users, the '*' value matches everything else, and capacity ceilings are refused rather than defaulted. This goes beyond the schema's own wording.

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?

States a specific verb and resource: 'Replace the WHOLE ownership routing configuration for one object,' and immediately decomposes what the config contains (deciding field, per-value pools, selection strategy). This clearly distinguishes it from the sibling read tool get_assignment_config and the run-creation tools.

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

Usage Guidelines5/5

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

Explicitly tells the agent to read the current config via get_assignment_config and send it back with changes, and names list_filterable_fields and list_crm_users as prerequisite calls. It also states a non-obvious allowed case (configuring a value no record holds) and the empty-list-clears behavior, covering when-not implicitly as well.

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