Skip to main content
Glama
kj455

MCP Kibela

by kj455

kibela_search_notes

Search and retrieve Kibela notes using a specific query with the MCP Kibela server. Access stored information quickly to support note management and updates.

Instructions

Search Kibela notes by query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query

Implementation Reference

  • The handler function that implements the core logic of the 'kibela_search_notes' tool. It validates the query input, fetches notes via the searchNotes GraphQL helper, processes the response to extract document nodes, and returns the notes as a JSON-formatted text content block.
    handler: async (args) => {
      if (!args.query) {
        throw new Error('Query is required')
      }
    
      const response = await searchNotes({ query: args.query })
    
      const edges = response.search?.edges ?? []
      const notes = edges
        .filter((edge): edge is NonNullable<(typeof edges)[number]> => edge != null)
        .filter((edge) => edge.node?.document != null)
        .map((edge) => edge.node?.document)
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(notes, null, 2),
          },
        ],
      }
    },
  • The tool metadata including name, description, and input schema for validating the 'query' parameter.
    tool: {
      name: 'kibela_search_notes',
      description: 'Search Kibela notes by query',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query',
          },
        },
        required: ['query'],
      },
    },
  • Registers 'kibela_search_notes' by mapping it to searchNotesTool in the central toolDefinitions object, enabling lookup and execution via handleToolRequest.
    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
  • Supporting GraphQL utility function called by the tool handler to perform the actual note search query.
    export async function searchNotes(variables: SearchNotesVariables): Promise<SearchNotesResponse> {
      return gqlRequest(searchNotesQuery, variables)
    }
  • GraphQL query document used by the searchNotes helper to fetch notes by query.
    const searchNotesQuery: TypedDocumentNode<SearchNotesResponse, SearchNotesVariables> = gql`
      query SearchNotes($query: String!) {
        search(query: $query, first: 15) {
          edges {
            node {
              document {
                ... on Note {
                  id
                  title
                  url
                }
              }
            }
          }
        }
      }
    `
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 only states the basic action ('search') without detailing aspects like search scope (e.g., across all notes or limited), result format, pagination, authentication needs, or rate limits, leaving significant gaps for a tool with no structured safety hints.

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 just four words, front-loading the key action and resource without any wasted words. It efficiently conveys the core purpose in a single, clear phrase.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the search returns (e.g., note summaries, IDs, or full content), how results are ordered, or any limitations, which are critical for a search tool with no structured output documentation.

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 query', which aligns with the single parameter 'query' in the schema. Since schema description coverage is 100% (the parameter is documented as 'Search query'), the description adds minimal value beyond what the schema provides, meeting the baseline for high 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 verb ('search') and resource ('Kibela notes'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'kibela_get_my_notes' or 'kibela_get_note_from_path', which also retrieve notes but with different scopes or methods.

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 when to prefer this search tool over other note-retrieval siblings like 'kibela_get_my_notes' (for user-specific notes) or 'kibela_get_note_from_path' (for path-based lookup).

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