Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_get_recently_viewed_notes

Fetch up to 15 recently viewed notes from Kibela to quickly access your recent activity.

Instructions

Get your recently viewed notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of notes to fetch (max 15)

Implementation Reference

  • src/kibela.ts:161-174 (registration)
    Tool definition/registration constant with name, description, and input schema
    const GET_RECENTLY_VIEWED_NOTES_TOOL: Tool = {
      name: "kibela_get_recently_viewed_notes",
      description: "Get your recently viewed notes",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Number of notes to fetch (max 15)",
            default: 15,
          },
        },
      },
    };
  • Handler case in CallToolRequestSchema switch statement that executes the GraphQL query to fetch recently viewed notes
    case "kibela_get_recently_viewed_notes": {
      const limit = (args.limit as number) || 15;
      const operation = `
        query GetRecentlyViewedNotes($limit: Int!) {
          noteBrowsingHistories(first: $limit) {
            nodes {
              note {
                id
                title
                url
                contentUpdatedAt
                author {
                  id
                  account
                  realName
                }
              }
            }
          }
        }
      `;
    
      const response = await client.request<RecentlyViewedNotesResponse>(operation, { limit });
      const notes = response.noteBrowsingHistories.nodes.map((node) => node.note);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(notes, null, 2),
          },
        ],
      };
    }
  • src/kibela.ts:218-219 (registration)
    Tool listed in the ListToolsRequestSchema handler (registration in tool list)
    GET_RECENTLY_VIEWED_NOTES_TOOL,
    GET_NOTE_FROM_PATH_TOOL,
  • TypeScript type for the GraphQL response of recently viewed notes
    export interface RecentlyViewedNotesResponse {
      noteBrowsingHistories: {
        nodes: Array<{
          note: KibelaNote;
        }>;
      };
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states it's a read operation implicitly. It does not explicitly disclose that it is read-only, or describe any edge cases like empty results or data freshness.

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?

A single sentence that is front-loaded and contains zero unnecessary words. Every word earns its place.

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 optional param, no output schema, no annotations), the description is minimally adequate. It lacks details on return format, ordering, or time scope, but the core purpose is clear.

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% for the single parameter 'limit', which is fully described in the schema. The tool description adds no additional meaning beyond the schema, hence baseline 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 clearly states the action ('Get') and the resource ('your recently viewed notes'), distinguishing it from sibling tools like kibela_get_my_notes by specifying 'recently viewed'.

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 like kibela_get_my_notes or kibela_search_notes. There is no mention of when not to use it.

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/kiwamizamurai/mcp-kibela-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server