Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_get_groups

Retrieve a list of groups you can access in Kibela, enabling group-specific queries and operations.

Instructions

Get list of accessible groups

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool schema/definition for kibela_get_groups with no required input parameters.
    const GET_GROUPS_TOOL: Tool = {
      name: "kibela_get_groups",
      description: "Get list of accessible groups",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
  • src/kibela.ts:206-221 (registration)
    Registration of GET_GROUPS_TOOL in the list of 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,
      ],
    }));
  • Handler implementation: executes a GraphQL query to fetch up to 10 readable groups and returns them as JSON text.
    case "kibela_get_groups": {
      const operation = `
        query GetGroups {
          groups(first: 10, ability: READABLE) {
            nodes {
              id
              name
              description
              isPrivate
              canBeManaged
              canBeJoinedBySelf
              isJoined
            }
          }
        }
      `;
    
      const response = await client.request<GroupResponse>(operation);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.groups.nodes, null, 2),
          },
        ],
      };
    }
  • Type definition for the GraphQL response containing groups.
    export interface GroupResponse {
      groups: {
        nodes: KibelaGroup[];
      };
    }
  • Type definition for a Kibela group object returned by the API.
    export interface KibelaGroup {
      id: string;
      name: string;
      description?: string;
      isPrivate?: boolean;
      canBeManaged?: boolean;
      canBeJoinedBySelf?: boolean;
      isJoined?: boolean;
    }
Behavior2/5

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

No annotations are provided, and the description only says 'get list', lacking details on pagination, ordering, permission requirements, or whether the list is complete. For a read-only tool, this is insufficient transparency.

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 concise sentence that front-loads the action and resource, with no unnecessary words.

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 return values. It only says 'list of groups', not what properties each group has (e.g., id, name). This leaves the agent guessing about the response format.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds the purpose ('list of accessible groups') beyond the empty schema, but does not specify any parameter context since none exist.

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 clearly states the verb 'Get' and the resource 'list of accessible groups', making the tool's purpose immediately understandable. It distinguishes itself from sibling tools like kibela_get_group_folders and kibela_get_users.

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 on when to use this tool versus alternatives like kibela_get_group_folders or kibela_get_users. The description does not mention usage context or exclusions.

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