Skip to main content
Glama

Set a Role's Requests

set_role_requests
DestructiveIdempotent

Replace the approved Requests Member, a custom Role or End users in selected mode may list and execute. The list you pass is the whole direct grant list. Requests from apps shared with the Role remain reachable. Every id must be an approved, enabled Request in this Project.

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": {
      "role_id": "<role_id>",
      "request_ids": "<request_ids>"
    },
    "name": "set_role_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesUUID of the Role
request_idsYesUUIDs of the approved Requests to grant

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description earns credit by spelling out the actual blast radius — the prior direct grant list is replaced entirely — and by adding a precondition ('every id must be an approved, enabled Request in this Project') that the annotations cannot convey.

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?

Three sentences, front-loaded with the replace operation, and each sentence carries information (scope, replacement semantics, shared-app exception, validation rule). The first sentence's tangled syntax is the only real cost; there is no filler.

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 two-parameter destructive mutation with no output schema, the description covers what is overwritten, what survives, and what input is valid, which is most of what an agent needs. Missing only secondary details such as required permission level or behavior when an id fails validation.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, establishing a baseline of 3. The description adds meaningful constraint on request_ids (must be approved, enabled, and in this Project) and clarifies that the array is a complete replacement set, but says nothing additional about role_id beyond what the schema provides.

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 names a specific operation and resource: replacing the set of approved Requests that members, custom Roles, or end users can list and execute. The opening sentence is grammatically convoluted ('Replace the approved Requests Member, a custom Role or End users in selected mode may list and execute'), which slows parsing, but the verb+resource pairing is still recoverable and distinguishable from siblings like add_role_members or set_app_access.

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?

It gives the crucial usage context that 'the list you pass is the whole direct grant list', which tells an agent this is a wholesale replace rather than an additive grant, and notes that Requests from shared apps remain reachable. It does not explicitly contrast with sibling tools that also modify role grants or state when not to use it, so it stops short of full routing guidance.

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