Skip to main content
Glama
kj455

MCP Kibela

by kj455

kibela_get_note_content

Retrieve specific note content from Kibela by providing its note ID, enabling efficient data access and information management within the MCP Kibela server.

Instructions

Get note content by note ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNote ID

Implementation Reference

  • The handler function for the 'kibela_get_note_content' tool. It validates the note ID, fetches the note using the getNote GraphQL function, and returns the note data as a JSON-formatted text content block.
    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),
          },
        ],
      }
    },
  • The schema definition for the tool, including name, description, and input schema requiring a 'id' string parameter.
      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 all tools including 'kibela_get_note_content' mapped to its tool definition in the central toolDefinitions object.
    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 to retrieve a note by ID, used by the tool handler.
    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 provided, so the description carries the full burden of behavioral disclosure. It states 'Get note content', implying a read-only operation, but doesn't clarify aspects like authentication needs, rate limits, error handling, or what 'content' includes (e.g., text, metadata). For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes directly to understanding the tool's purpose.

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 (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic action and parameter but lacks details on behavioral traits (e.g., permissions, output format) that would be helpful for an agent. Without annotations or an output schema, the description should do more to compensate, but it doesn't fully address these gaps.

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 description mentions 'by note ID', which aligns with the single parameter 'id' in the schema. Since schema description coverage is 100% (the parameter is documented as 'Note ID'), the description adds minimal value beyond what the schema provides. With high coverage, the baseline is 3, and the description doesn't compensate with additional details like format or constraints.

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 ('note content'), making the purpose understandable. It specifies retrieval by 'note ID', which distinguishes it from sibling tools like 'kibela_get_note_from_path' (which uses a path) and 'kibela_search_notes' (which involves searching). However, it doesn't explicitly differentiate from 'kibela_get_my_notes' (which might list notes vs. get content), so it's not fully sibling-distinctive.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a note ID), exclusions, or comparisons to siblings like 'kibela_get_note_from_path' (for path-based access) or 'kibela_get_my_notes' (for listing). Usage is implied by the action but not explicitly stated.

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