Skip to main content
Glama
kj455

MCP Kibela

by kj455

kibela_get_note_content

Retrieve the full content of a Kibela note by providing its note ID.

Instructions

Get note content by note ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNote ID

Implementation Reference

  • The handler function that executes the kibela_get_note_content tool logic. It takes an id argument, calls getNote to fetch the note, and returns the note content as JSON.
      handler: async (args) => {
        if (!args.id) {
          throw new Error('Note ID is required')
        }
    
        const response = await getNote({ id: args.id })
    
        if (!response.note) {
          throw new Error('Note not found')
        }
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.note, null, 2),
            },
          ],
        }
      },
    }
  • Type definition for GetNoteContentArgs (id: string) and the inputSchema for the tool defining the required 'id' string parameter.
    export type GetNoteContentArgs = {
      id: string
    }
    
    export const getNoteContentTool: ToolDefinition<GetNoteContentArgs> = {
      tool: {
        name: 'kibela_get_note_content',
        description: 'Get note content by note ID',
        inputSchema: {
          type: 'object',
          properties: {
            id: {
              type: 'string',
              description: 'Note ID',
            },
          },
          required: ['id'],
        },
  • Registration of kibela_get_note_content in the tool definitions map, mapping the tool name to the getNoteContentTool definition.
      kibela_get_note_content: getNoteContentTool,
      kibela_get_note_from_path: getNoteFromPathTool,
      kibela_update_note_content: updateNoteContentTool,
      kibela_create_note: createNoteTool,
    } as const
  • Generic ToolDefinition type used to define the tool's schema and handler structure.
    import { Tool } from '@modelcontextprotocol/sdk/types.js'
    
    export type ToolResponse = {
      content: {
        type: 'text'
        text: string
      }[]
      isError?: boolean
      _meta?: { [x: string]: unknown }
    }
    
    export type ToolHandler<T> = (args: T) => Promise<ToolResponse>
    
    export type ToolDefinition<T> = {
      tool: Tool
      handler: ToolHandler<T>
    }
  • GraphQL query getNote that fetches note by ID, called by the handler to retrieve note data.
    const getNoteQuery: TypedDocumentNode<GetNoteResponse, GetNoteVariables> = gql`
      query GetNote($id: ID!) {
        note(id: $id) {
          id
          title
          content
        }
      }
    `
    
    export async function getNote(variables: GetNoteVariables): Promise<GetNoteResponse> {
      return gqlRequest(getNoteQuery, variables)
    }
Behavior2/5

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

No annotations are present, so the description carries full burden for behavioral disclosure. It only states the basic action without detailing what is returned (e.g., full note content vs. metadata), whether authentication is needed, or error handling for invalid IDs. This is insufficient for a tool that likely requires certain permissions.

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 very short (one sentence) and directly to the point. While it lacks structure (e.g., sections or bullet points), its brevity is acceptable for a simple tool. No unnecessary words are present.

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 required parameter, no output schema), the description is minimally adequate. However, it could be improved by specifying what the response contains (e.g., 'Returns the note content as a string') and noting potential errors. Overall, it covers the essential purpose but not the full context.

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% (the parameter 'id' has a description 'Note ID'). The description reiterates this with 'by note ID', which adds no new meaning. Baseline score of 3 is appropriate since the schema already provides the necessary detail.

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 explicitly states the action ('Get'), resource ('note content'), and identifier ('by note ID'). It clearly distinguishes from sibling tools like 'kibela_create_note' (create), 'kibela_search_notes' (search), and 'kibela_get_note_from_path' (different retrieval method).

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. There is no mention of use cases, such as retrieving full content versus summaries from 'kibela_get_my_notes', or when to prefer path-based retrieval via 'kibela_get_note_from_path'.

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