Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_get_my_notes

Retrieve your most recent notes from Kibela, with an option to limit the number fetched up to 50.

Instructions

Get your latest notes from Kibela

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of notes to fetch (max 50)

Implementation Reference

  • Tool definition (name, description, inputSchema) for kibela_get_my_notes. It accepts an optional 'limit' number (default 15, max 50).
    const GET_MY_NOTES_TOOL: Tool = {
      name: "kibela_get_my_notes",
      description: "Get your latest notes from Kibela",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Number of notes to fetch (max 50)",
            default: 15,
          },
        },
      },
    };
  • src/kibela.ts:206-221 (registration)
    Tool registration via ListToolsRequestSchema handler, including GET_MY_NOTES_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 for kibela_get_my_notes. Executes a GraphQL query 'GetMyNotes' via currentUser.latestNotes, extracts notes from the response, and returns them as JSON text.
    case "kibela_get_my_notes": {
      const limit = (args.limit as number) || 15;
      const operation = `
        query GetMyNotes($limit: Int!) {
          currentUser {
            latestNotes(first: $limit) {
              totalCount
              edges {
                node {
                  id
                  title
                  url
                  contentUpdatedAt
                  author {
                    id
                    account
                    realName
                  }
                }
              }
            }
          }
        }
      `;
    
      const response = await client.request<NotesResponse>(operation, { limit });
      const notes = response.currentUser.latestNotes.edges.map((edge) => edge.node);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(notes, null, 2),
          },
        ],
      };
    }
  • TypeScript type NotesResponse used to type the GraphQL response from the GetMyNotes query.
    export interface NotesResponse {
      currentUser: {
        latestNotes: {
          totalCount: number;
          edges: Array<{
            node: KibelaNote;
          }>;
        };
      };
    }
Behavior2/5

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

No annotations are present, and the description only states the purpose without disclosing behavioral traits such as read-only nature, authentication requirements, rate limits, or result ordering. The description carries the full burden but fails to provide any such details.

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 sentence of five words, front-loaded with the core purpose. Every word earns its place, with no redundancy or unnecessary detail.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description is minimally adequate. However, it omits useful context like ordering (e.g., creation date descending) or the set of fields returned, which could help the agent understand the tool's full behavior.

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 100% schema description coverage, the input schema already fully documents the 'limit' parameter (type, default). The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 your latest notes from Kibela' uses a specific verb ('Get') and resource ('your latest notes'), clearly differentiating it from siblings like 'kibela_search_notes' (search all) and 'kibela_get_recently_viewed_notes' (recently viewed, not owned).

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?

The description implies usage for retrieving the user's own notes but provides no explicit guidance on when to use this tool versus alternatives (e.g., search_notes for broader queries or get_note_content for a single note). No exclusions or context provided.

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