Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_get_group_notes

Retrieve notes without any folder assignment from a specified group in Kibela using the group ID.

Instructions

Get notes in a group that are not attached to any folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesGroup ID

Implementation Reference

  • Tool definition with inputSchema for kibela_get_group_notes: requires groupId (string).
    const GET_GROUP_NOTES_TOOL: Tool = {
      name: "kibela_get_group_notes",
      description: "Get notes in a group that are not attached to any folder",
      inputSchema: {
        type: "object",
        properties: {
          groupId: { type: "string", description: "Group ID" },
        },
        required: ["groupId"],
      },
    };
  • src/kibela.ts:206-221 (registration)
    Tool is registered in the ListToolsRequestSchema handler, included in the tools array.
    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 case for kibela_get_group_notes in the CallToolRequestSchema switch: executes GraphQL query to fetch group notes not attached to any folder.
    case "kibela_get_group_notes": {
      const { groupId } = args as { groupId: string };
    
      const operation = `
        query GetGroupNotes($groupId: ID!) {
          group(id: $groupId) {
            notes(first: 10, active: true, onlyNotAttachedFolder: true, orderBy: { field: CONTENT_UPDATED_AT, direction: DESC }) {
              nodes {
                id
                title
                contentUpdatedAt
                publishedAt
                author {
                  account
                  realName
                }
              }
            }
          }
        }
      `;
    
      const response = await client.request<GroupNotesResponse>(operation, { groupId });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.group.notes.nodes, null, 2),
          },
        ],
      };
    }
  • TypeScript interface for the GraphQL response shape returned by the handler.
    export interface GroupNotesResponse {
      group: {
        notes: {
          nodes: {
            id: string;
            title: string;
            contentUpdatedAt: string;
            publishedAt: string;
            author: {
              account: string;
              realName: string;
            };
          }[];
        };
      };
    }
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits such as permissions, error handling, or limitations. The simple statement lacks depth.

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 a single sentence, front-loaded with the action. It is concise, though slightly under-specified; still, no unnecessary words.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is adequate but incomplete. It does not explain the return format or behavior on error, leaving gaps for the agent.

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?

Schema coverage is 100%, so the description adds no extra meaning beyond the schema. The baseline of 3 applies as the description is not misleading but adds no value.

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 uses a specific verb ('Get') and resource ('notes in a group') with a qualifier ('not attached to any folder'), clearly distinguishing it from sibling tools like 'kibela_get_folder_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 vs. alternatives, nor any conditions or exclusions. The description simply states what it does without context.

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