Skip to main content
Glama

list_roles

Retrieve a paginated listing of user roles from the BookStack wiki system to manage permissions and access controls.

Instructions

Get a listing of roles in the system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
countNoNumber of items per page
sortNoSort parameter

Implementation Reference

  • Core execution logic for the 'list_roles' tool: parses pagination parameters from input, fetches roles using BookStackClient.getRoles(), and formats the paginated response.
    case "list_roles": {
      const params = PaginationSchema.parse(args);
      const result = await client.getRoles(params);
      return formatApiResponse(result.data, result.total);
    }
  • Tool schema definition for 'list_roles', including name, description, and input schema for optional pagination and sorting parameters. Part of the tools array returned by createSearchAndUserTools().
    {
      name: "list_roles",
      description: "Get a listing of roles in the system",
      inputSchema: {
        type: "object",
        properties: {
          page: { type: "number", description: "Page number for pagination" },
          count: { type: "number", description: "Number of items per page" },
          sort: { type: "string", description: "Sort parameter" },
        },
      },
    },
  • src/index.ts:103-128 (registration)
    Registers 'list_roles' by listing it in searchUserToolNames array and routing tool execution requests to handleSearchAndUserTool() in the main MCP server request handler.
    const searchUserToolNames = [
      "search_all",
      "list_users",
      "get_user",
      "create_user",
      "update_user",
      "delete_user",
      "list_roles",
      "get_role",
      "create_role",
      "update_role",
      "delete_role",
      "list_attachments",
      "get_attachment",
      "delete_attachment",
      "list_images",
      "get_image",
      "update_image",
      "delete_image",
    ];
    
    if (contentToolNames.includes(name)) {
      result = await handleContentTool(name, args, bookStackClient);
    } else if (searchUserToolNames.includes(name)) {
      result = await handleSearchAndUserTool(name, args, bookStackClient);
    } else {
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('Get'), but doesn't mention whether it's paginated (though parameters imply it), what the return format is, or any rate limits or permissions needed. This leaves significant gaps for a tool that likely interacts with system data.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a tool that lists system roles with no annotations and no output schema, the description is inadequate. It doesn't explain what data is returned, how results are structured, or any behavioral nuances like pagination defaults or error handling. This leaves too much uncertainty for effective use.

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?

The input schema has 100% description coverage, clearly documenting all three parameters (page, count, sort). The description adds no additional semantic context beyond implying a listing operation, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for any gaps.

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 clearly states the verb ('Get') and resource ('listing of roles in the system'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its sibling 'get_role' (which likely retrieves a single role), leaving some ambiguity about when to use one versus the other.

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 description provides no guidance on when to use this tool versus alternatives like 'get_role' or 'search_all'. It lacks context about prerequisites, such as whether authentication is required, and doesn't mention any exclusions or specific scenarios where this tool is preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lautarobarba/bookstack_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server