Skip to main content
Glama
kj455

MCP Kibela

by kj455

kibela_get_my_notes

Retrieve your most recent notes from Kibela, with customizable limits, using the MCP Kibela server to streamline access and organization of information.

Instructions

Get my latest notes from Kibela

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of notes to fetch

Implementation Reference

  • The async handler function that processes input arguments, fetches the user's latest notes via GraphQL query, filters and maps the response, and returns the notes as a formatted JSON string in a tool response content block.
    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),
          },
        ],
      }
    },
  • The tool schema definition, including the name 'kibela_get_my_notes', description, and input schema for the optional 'limit' parameter with default 10.
    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,
          },
        },
      },
    },
  • Registration of all tools, including 'kibela_get_my_notes' mapped to getMyNotesTool, in the toolDefinitions object used for dispatching tool requests.
    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
  • Helper function that executes the GraphQL query for fetching the current user's latest notes, used by the tool handler.
    export async function getMyNotes(variables: GetMyNotesVariables): Promise<GetMyNotesResponse> {
      return gqlRequest(getMyNotesQuery, variables)
    }
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool retrieves notes but lacks details on permissions, rate limits, pagination, or error handling. The phrase 'latest notes' hints at ordering, but this isn't explicitly defined, leaving gaps in understanding the tool's behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage guidelines, behavioral traits, and output format, which could hinder effective agent use in more complex scenarios.

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?

The input schema has 100% description coverage, with the 'limit' parameter clearly documented. The description doesn't add any semantic details beyond what the schema provides, such as default behavior or usage context for the limit. This meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Get') and resource ('my latest notes from Kibela'), making the purpose understandable. It doesn't explicitly differentiate from siblings like 'kibela_search_notes' or 'kibela_get_note_content', but the focus on 'my latest' provides some distinction.

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 like 'kibela_search_notes' or 'kibela_get_note_content'. The description implies it's for retrieving the user's recent notes, but it doesn't specify contexts, exclusions, or comparisons to sibling tools.

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

Related 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