Skip to main content
Glama
Sign In
Semaphore UI MCP server

Semaphore UI MCP server

by johsem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_global_role

DestructiveIdempotent

Update a global role's name, slug, and permissions through Semaphore UI's API, including optional project assignment when needed.

Instructions

update global role. Availability depends on Semaphore edition, license, and permissions; some Community routes return 404 or empty lists. PUT /roles/{role_slug}. Supply API fields in body; JSON-encoded string fields must remain strings.

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_slug": "<role_slug>",
      "body": "<body>"
    },
    "name": "update_global_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
role_slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare destructiveness, idempotency, and open-world behavior, so the bar is lower. The description adds meaningful operational context about edition/license restrictions and Community-edition 404/empty-list behavior, which is exactly the kind of runtime caveat annotations cannot express.

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?

The description is short and front-loads the identity of the tool and its availability caveat. The endpoint and body-encoding notes are useful, though the sentence fragment 'update global role.' is slightly terse for an opener.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool takes a required nested body object, has no output schema, and has completely undocumented parameters. The description does not explain the body shape, required fields, replacement semantics implied by PUT, or response behavior, leaving significant gaps for an agent to infer.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It only says to supply API fields in the body and that JSON-encoded string fields must remain strings, without explaining role_slug, the required body fields, or how permissions is represented.

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 states a specific verb and resource ('update global role'), and the 'global' qualifier implicitly separates it from update_project_role. It lacks an explicit contrast with siblings, which keeps it below a 5.

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?

The availability caveat (edition, license, permissions, Community 404s) gives useful context but does not say when to choose this tool over alternatives or what prerequisites are needed before calling it. No exclusions or routing guidance are 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