Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List roles

list_roles
Read-only

List workspace roles and their granted permissions in a read-only view to clarify who can do what.

Instructions

List the roles defined in this workspace and the permissions each one grants. Read-only. Useful for understanding who can do what.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.73.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'Read-only.' sentence largely repeats structured data. It does add that permissions are included per role, which is useful behavioral context, but says nothing about result size, ordering, or whether roles include built-in/system roles.

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 short sentences, front-loaded with the core action and result content. The only near-waste is 'Read-only.', which duplicates the readOnlyHint annotation, but it is a single short clause.

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 zero-parameter, read-only listing tool with no output schema, the description covers what is listed and what each entry includes. It could note whether results are paginated or whether system roles are included, but nothing essential is missing.

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?

The tool takes zero parameters, so the schema carries no semantics to compensate for; the baseline is 4. The description correctly frames the implicit scope as 'this workspace', which is the only parameter-like concept relevant here.

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?

States a specific verb and resource ('List the roles defined in this workspace') and adds what the result contains ('the permissions each one grants'). That is enough to separate it from siblings like list_team or list_models, though it does not explicitly name a near-miss alternative.

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?

'Useful for understanding who can do what' implies the use case (permission inspection) but gives no explicit when-not guidance, no prerequisites, and no pointer to related tools for editing or assigning roles. Usage is inferable rather than stated.

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