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

mcp-server-rt

Official
by bestpractical
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

grant_rights

Destructive

Grant user or group permissions on queues, custom fields, groups, classes, catalogs, or globally. Supports single rights or bulk grants; returns conflict error if already granted.

Instructions

Grant rights on a queue, custom field, group, class, catalog, or globally. Specify a single right with Right + (User or Group), or pass an array of grants for bulk operation. Returns 409 if a right is already granted.

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": {
      "object_type": "<object_type>"
    },
    "name": "grant_rights"
  }
}

Input Schema

NameRequiredDescriptionDefault
UserNoUsername or user ID to grant to (for single grant)
GroupNoGroup name or ID to grant to (for single grant)
RightNoRight name (for single grant)
grantsNoArray of grants for bulk operation. Each item: {Right, User or Group}
object_idNoObject ID, or name for a queue, class or catalog (group and customfield are numeric id only). Not needed for global.
object_typeYesType of object

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

destructiveHint=true already signals mutation, and the description adds the useful conflict behavior 'Returns 409 if a right is already granted.' It does not disclose permission requirements, reversibility, or success response details, but the added 409 context gives some behavioral transparency beyond the annotation alone.

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?

Three short sentences with no filler: the main action and targets come first, then the two invocation modes, then the conflict behavior. Every sentence earns its place and the structure is easy to scan.

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 six-parameter mutating tool, it covers both call shapes, all six object types, and the duplicate-grant outcome. It could add more about permissions or reversibility, but the current information is sufficient for correct invocation when combined with the schema.

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 description coverage is 100%, so the schema carries most parameter meaning, but the description adds conditional usage semantics: a single grant pairs Right with User or Group, while bulk uses the grants array. It also reinforces that global is a valid object type, which helps construct valid calls.

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 opens with a specific action ('Grant rights') and enumerates every target object type it applies to: queue, custom field, group, class, catalog, or global. It is clearly distinct from the sibling revoke_right by semantic polarity, though it does not name that 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?

It gives explicit usage modes ('Specify a single right with Right + (User or Group), or pass an array of grants for bulk operation') and lists object types. However, it does not state when to choose this tool over revoke_right or get_available_rights/list_rights; the selection guidance is implied rather than explicit.

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