Skip to main content
Glama
kj455

MCP Kibela

by kj455

kibela_get_note_from_path

Retrieve a Kibela note's full content by providing its path (e.g., /notes/123). Access note data directly via this tool.

Instructions

Get note content by note path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesNote path (e.g. /notes/123)

Implementation Reference

  • The handler function that executes the tool logic. Validates path argument, calls the GQL query getNoteFromPath, and returns the note content as JSON.
      handler: async (args) => {
        if (!args.path) {
          throw new Error('Note path is required')
        }
    
        const response = await getNoteFromPath({ path: args.path })
    
        if (!response.noteFromPath) {
          throw new Error('Note not found')
        }
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.noteFromPath, null, 2),
            },
          ],
        }
      },
    }
  • Input schema for the tool. Defines 'path' as a required string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        path: {
          type: 'string',
          description: 'Note path (e.g. /notes/123)',
        },
      },
      required: ['path'],
    },
  • GraphQL query definition and execution function for noteFromPath. Contains the query string and the async function that makes the GQL request.
    const getNoteFromPathQuery: TypedDocumentNode<GetNoteFromPathResponse, GetNoteFromPathVariables> = gql`
      query GetNoteFromPath($path: String!) {
        noteFromPath(path: $path) {
          id
          title
          content
        }
      }
    `
    
    export async function getNoteFromPath(variables: GetNoteFromPathVariables): Promise<GetNoteFromPathResponse> {
      return gqlRequest(getNoteFromPathQuery, variables)
    }
  • Registration of 'kibela_get_note_from_path' in the toolDefinitions map, mapping it to getNoteFromPathTool.
      kibela_get_note_from_path: getNoteFromPathTool,
      kibela_update_note_content: updateNoteContentTool,
      kibela_create_note: createNoteTool,
    } as const
Behavior2/5

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

No annotations provided, so the description carries full burden. It only implies a read operation ('get') but does not explicitly state that it is read-only, has no side effects, or any prerequisites. The minimal description leaves behavioral traits underspecified.

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 extremely concise with one front-loaded sentence that clearly states the purpose. Every word is essential, no redundancy.

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 (1 param, no output schema), the description covers the basic action but lacks details about return value or behavior. For a fully complete description, it should mention what the output contains (e.g., note content as text).

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 description coverage is 100% for the single 'path' parameter, with an example provided. The description adds no additional meaning beyond the schema, leading to a baseline score of 3.

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 note content by note path' specifies a clear verb (get), resource (note content), and method (by path). It distinguishes from siblings like kibela_get_note_content (likely by ID) by emphasizing the path-based retrieval.

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 implicitly indicates use when a note path is available, but lacks explicit guidance on when not to use or alternatives (e.g., if note ID is known, use kibela_get_note_content instead). This is a missed opportunity for clarity.

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