Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_get_users

Fetch the complete list of users from Kibela to manage team members and access profiles.

Instructions

Get list of users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The case handler for 'kibela_get_users' that executes a GraphQL query to fetch users and returns their id, account, and realName fields.
    case "kibela_get_users": {
      const operation = `
        query GetUsers {
          users(first: 100) {
            nodes {
              id
              account
              realName
            }
          }
        }
      `;
    
      const response = await client.request<UsersResponse>(operation);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.users.nodes, null, 2),
          },
        ],
      };
    }
  • The Tool definition for 'kibela_get_users' with name, description, and an empty inputSchema (no parameters required).
    const GET_USERS_TOOL: Tool = {
      name: "kibela_get_users",
      description: "Get list of users",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
  • src/kibela.ts:206-221 (registration)
    Registration of GET_USERS_TOOL in the ListToolsRequestSchema handler, listing it as one of the available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        SEARCH_NOTES_TOOL,
        GET_MY_NOTES_TOOL,
        GET_NOTE_CONTENT_TOOL,
        GET_GROUPS_TOOL,
        GET_GROUP_FOLDERS_TOOL,
        GET_GROUP_NOTES_TOOL,
        GET_FOLDER_NOTES_TOOL,
        GET_USERS_TOOL,
        LIKE_NOTE_TOOL,
        UNLIKE_NOTE_TOOL,
        GET_RECENTLY_VIEWED_NOTES_TOOL,
        GET_NOTE_FROM_PATH_TOOL,
      ],
    }));
  • The KibelaUser interface defining the shape of a user (id, account, realName), used as the return type.
    export interface KibelaUser {
      id: string;
      account: string;
      realName: string;
    }
  • The UsersResponse interface used for parsing the GraphQL response containing users.
    export interface UsersResponse {
      users: {
        nodes: KibelaUser[];
      };
    }
Behavior1/5

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

No annotations are present, and the description merely states 'Get list of users' without disclosing any behavioral traits such as side effects, authentication requirements, or return format. The agent has no insight beyond the operation type.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise but is essentially a restatement of the tool name. It does not earn its place by providing additional value, and it could be more informative without increasing length.

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?

Given no output schema, the description should explain what the list contains (e.g., IDs, names) and any default behavior. It fails to do so, leaving the agent uncertain about the tool's output.

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?

With no parameters and 100% schema coverage, the description adds minimal value beyond the schema. It states the resource type but does not elaborate on user representation or filtering, so it stays at the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get list of users' clearly states the verb 'Get' and resource 'list of users', which is precise and distinguishes from sibling tools that deal with folders, groups, or notes.

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?

No guidance is provided on when to use this tool or when to prefer alternatives. The description lacks context about prerequisites or use cases, relying solely on the tool name.

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/kiwamizamurai/mcp-kibela-server'

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