Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set customer company role

set_customer_company_role
Destructive

Assign a customer an admin or buyer role in their current company to control order visibility; admin sees all company orders, buyer only their own.

Instructions

Give a customer a company role in the company they belong to now. Roles come from the workspace's catalogue; v1 has two: 'admin' sees every order placed for the company, 'buyer' (the default) only their own. The role holds only while the customer stays in that company - moved to another, they are buyer there. Refused when the customer has no company, and for a key outside the catalogue. Returns the customer with companyRole as the effective role.

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": {
      "id": "<id>",
      "role": "<role>"
    },
    "name": "set_customer_company_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe customer's id (from list_customers)
roleYesA role key from the workspace's company role catalogue - v1: 'admin' or 'buyer'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write nature is known. The description adds real behavioral context beyond that: the role is scoped to the current company membership, silently degrades to 'buyer' if the customer moves, and is rejected when the customer has no company or the key is unknown. It does not explicitly warn that an existing role is overwritten, which is the main gap given destructiveHint=true.

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?

Four tight sentences, front-loaded with the action and scope, then role semantics, then persistence caveat, then refusal and return behavior. Nothing is repeated and every sentence carries information an agent needs.

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?

No output schema exists, and the description compensates by stating the return value (the customer with companyRole as the effective role). Combined with the refusal cases and membership-scoping rule, an agent has everything needed to call this correctly and interpret the result.

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 baseline is 3, but the description earns extra credit by explaining what each role key means: 'admin' sees every order for the company, 'buyer' only their own. That semantic content is not in the schema, whose role field only lists the two keys without describing their effect.

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: 'Give a customer a company role in the company they belong to now.' The scope (current company only) is baked into the first sentence, and no sibling tool in the list could be confused with this operation.

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?

Provides clear context for use: the customer must belong to a company, the role must be in the workspace catalogue, and 'buyer' is the default. It also states the two refusal conditions, which functions as when-not guidance. It does not name an alternative tool, but none of the listed siblings performs the same action.

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

Deploy Server

Other Tools