Skip to main content
Glama
kj455

MCP Kibela

by kj455

kibela_create_note

Create and manage notes in Kibela by specifying title, content, folders, and groups. Enable co-editing, draft mode, and assign authors for collaborative documentation.

Instructions

Create a new note in Kibela.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorIdNoID of the author of the note. If not specified, the note will be created by the authenticated user.
coeditingNorequired: Whether to enable co-editing for the note
contentYesrequired: Content of the note in markdown format
draftNoWhether to create the note as a draft
foldersNoIDs of the folders to add the note to.
groupIdsNorequired: IDs of the groups to create the note in.
titleYesrequired: Title of the note

Implementation Reference

  • The handler function for 'kibela_create_note' tool that validates required parameters and calls the GraphQL 'createNote' mutation to create the note.
    handler: async ({ title, content, groupIds, folders, authorId, coediting, draft }) => {
      if (!title || !content || !groupIds || !coediting) {
        throw new Error('Title, content, groupIds, and coediting are required')
      }
    
      const response = await createNote({
        input: {
          clientMutationId: uuid(),
          title,
          content,
          groupIds,
          folders,
          authorId,
          coediting,
          draft,
        },
      })
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.createNote, null, 2),
          },
        ],
      }
    },
  • The tool definition including name, description, and input schema for parameter validation.
    tool: {
      name: 'kibela_create_note',
      description: 'Create a new note in Kibela.',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'required: Title of the note',
          },
          content: {
            type: 'string',
            description: 'required: Content of the note in markdown format',
          },
          groupIds: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'required: IDs of the groups to create the note in.',
          },
          folders: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'IDs of the folders to add the note to.',
          },
          authorId: {
            type: 'string',
            description:
              'ID of the author of the note. If not specified, the note will be created by the authenticated user.',
          },
          coediting: {
            type: 'boolean',
            description: 'required: Whether to enable co-editing for the note',
          },
          draft: {
            type: 'boolean',
            description: 'Whether to create the note as a draft',
          },
        },
        required: ['title', 'content'],
      },
    },
  • Registration of the 'kibela_create_note' tool by mapping it to createNoteTool in the 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
  • GraphQL mutation definition and helper function used by the tool handler to perform the actual note creation.
    const createNoteMutation: TypedDocumentNode<CreateNoteResponse, CreateNoteVariables> = gql`
      mutation CreateNote($input: CreateNoteInput!) {
        createNote(input: $input) {
          clientMutationId
          note {
            id
            title
            content
            url
          }
        }
      }
    `
    
    export async function createNote(variables: CreateNoteVariables): Promise<CreateNoteResponse> {
      return gqlRequest(createNoteMutation, variables)
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a note but offers no information about permissions required, rate limits, side effects, error conditions, or what happens on success. For a write operation with zero annotation coverage, 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?

The description is a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a straightforward creation tool and gets directly to the point.

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?

For a write operation with 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation, what permissions are needed, or how to handle the result. The agent must rely entirely on the input schema for operational details.

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%, so all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the structured fields. This meets the baseline expectation when the schema does the heavy lifting, but provides no extra value.

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 ('Create') and resource ('new note in Kibela'), making the purpose immediately understandable. It distinguishes this as a creation tool among siblings that include get, search, and update operations, though it doesn't explicitly contrast with them in the description text.

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 like kibela_update_note_content or kibela_search_notes. There's no mention of prerequisites, appropriate contexts, or exclusions, leaving the agent to infer usage solely from the tool name and sibling relationships.

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