Skip to main content
Glama
Sign In
tie-mcp-server

tie-mcp-server

by taherkaraki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_user_roles

Replace the role list assigned to a user with a new set of roles. Specify the user ID and the list of role IDs to update permissions.

Instructions

Replace role list for a user

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

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter: id
bodyYesUser roles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Term 'Replace' implies destructive overwrite of roles, but no details on permissions, side effects, or confirmation. No annotations to supplement, so description carries full burden.

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?

Single sentence, front-loaded, no extraneous words. Efficiently conveys core action.

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 simple tool with no output schema and two parameters, description is adequate. Lacks return value info and error handling, but functional completeness is sufficient.

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%. Description adds context that 'roles' array is the replacement list, beyond schema's generic 'Path parameter' and 'User roles'.

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?

Description clearly states verb 'Replace' and resource 'role list for a user', distinguishing it from siblings like 'update_user' and 'update_role'.

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?

No guidance on when to use this tool versus alternatives, such as 'update_user' which might also modify roles. No prerequisites or context provided.

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