Skip to main content
Glama
kj455

MCP Kibela

by kj455

kibela_get_my_notes

Fetches your recent notes from Kibela, with an optional limit on the number returned.

Instructions

Get my latest notes from Kibela

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of notes to fetch

Implementation Reference

  • Tool definition with handler for kibela_get_my_notes. Calls getMyNotes GraphQL query and returns notes as JSON text content.
    export const getMyNotesTool: ToolDefinition<GetMyNotesArgs> = {
      tool: {
        name: 'kibela_get_my_notes',
        description: 'Get my latest notes from Kibela',
        inputSchema: {
          type: 'object',
          properties: {
            limit: {
              type: 'number',
              description: 'Maximum number of notes to fetch',
              default: 10,
            },
          },
        },
      },
      handler: async (args) => {
        const limit = args.limit ?? 10
    
        const response = await getMyNotes({ limit })
    
        const edges = response.currentUser?.latestNotes?.edges ?? []
        const notes = edges
          .filter((edge): edge is NonNullable<(typeof edges)[number]> => edge != null)
          .filter((edge) => edge.node != null)
          .map((edge) => edge.node)
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(notes, null, 2),
            },
          ],
        }
      },
    }
  • Input type definition for the tool (optional limit parameter).
    export type GetMyNotesArgs = {
      limit?: number
    }
    
    export const getMyNotesTool: ToolDefinition<GetMyNotesArgs> = {
      tool: {
        name: 'kibela_get_my_notes',
        description: 'Get my latest notes from Kibela',
        inputSchema: {
          type: 'object',
          properties: {
            limit: {
              type: 'number',
              description: 'Maximum number of notes to fetch',
              default: 10,
            },
          },
        },
      },
  • Tool registration mapping the name 'kibela_get_my_notes' to getMyNotesTool.
    const toolDefinitions = {
      kibela_search_notes: searchNotesTool,
      kibela_get_my_notes: getMyNotesTool,
      kibela_get_note_content: getNoteContentTool,
      kibela_get_note_from_path: getNoteFromPathTool,
      kibela_update_note_content: updateNoteContentTool,
      kibela_create_note: createNoteTool,
    } as const
  • GraphQL query function that fetches the current user's latest notes from Kibela API.
    export async function getMyNotes(variables: GetMyNotesVariables): Promise<GetMyNotesResponse> {
      return gqlRequest(getMyNotesQuery, variables)
    }
  • Type definitions for the GraphQL query variables and response shape.
    type GetMyNotesResponse = {
      currentUser: {
        latestNotes: {
          totalCount: number
          edges: {
            node: {
              id: string
              title: string
              url: string
            }
          }[]
        }
      }
    }
    
    type GetMyNotesVariables = {
      limit: number
    }
Behavior2/5

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

With no annotations, the description bears full responsibility. It implies a read operation but does not disclose what constitutes 'latest' (e.g., creation time vs update time), whether authentication is needed, or what the response format looks like. This leaves significant behavioral gaps.

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?

A single sentence of 5 words conveys the purpose efficiently. No extraneous information; the action is front-loaded.

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?

Despite the simple parameter, the description fails to explain the structure of 'notes', the meaning of 'latest' (e.g., sorting order), or any pagination behavior implied by the limit parameter. With no output schema or annotations, the tool lacks sufficient detail for reliable agent 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?

Schema coverage is 100% with the 'limit' parameter clearly described in the schema. The description adds no extra meaning beyond the schema, so baseline 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 my latest notes from Kibela' clearly states the specific verb 'Get', the resource 'my latest notes', and the system 'Kibela'. It distinguishes from siblings like kibela_search_notes (search) and kibela_get_note_content (specific note content) by focusing on personal and recent 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 versus alternatives. The description does not mention when to prefer this over kibela_search_notes or kibela_get_note_from_path, nor does it specify any prerequisites or 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/kj455/mcp-kibela'

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