Skip to main content
Glama
ainote-dev

AI Note MCP Server

by ainote-dev

list_categories

Retrieve all available task categories within AI Note MCP Server to organize and manage tasks effectively using natural language commands.

Instructions

List all categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for 'list_categories' tool. Proxies the tool call to the backend API client.
    handler: async (_args, { apiClient }) => {
      const result = await apiClient.callTool('list_categories', {});
      return result;  // Return full result with { content: [...] }
    }
  • Schema definition for the 'list_categories' tool, including name, description, and input schema (no parameters).
    function listCategoriesDefinition() {
      return {
        name: 'list_categories',
        description: 'List all categories',
        inputSchema: {
          type: 'object',
          properties: {}
        }
      };
    }
  • Top-level registration of shared tools (including 'list_categories') to the ToolRegistry.
    function registerTools(registry, { includeChatGpt }) {
      registry.registerMany(getSharedTools());
    
      if (includeChatGpt) {
        registry.registerMany(getChatGptTools());
      }
    }
  • Specific registration entry for 'list_categories' tool in getSharedTools() array.
    {
      definition: listCategoriesDefinition(),
      handler: async (_args, { apiClient }) => {
        const result = await apiClient.callTool('list_categories', {});
        return result;  // Return full result with { content: [...] }
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'List all categories' but doesn't disclose behavioral traits such as whether it's read-only, paginated, rate-limited, or requires authentication. This is a significant gap for a tool with no annotation coverage.

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 a single sentence 'List all categories', which is front-loaded and wastes no words. Every part of the sentence directly contributes to the tool's purpose.

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 tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is incomplete. It doesn't explain return values, behavioral context, or how it fits with siblings, leaving gaps in understanding for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is acceptable given the lack of parameters, aligning with the baseline for 0 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all categories' clearly states the action (list) and resource (categories), but it's vague about scope and doesn't distinguish from sibling tools like 'list_tasks'. It's not tautological but lacks specificity about what 'all' means in this context.

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 'list_tasks' or other siblings. The description implies usage for retrieving categories but doesn't specify context, prerequisites, or exclusions.

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/ainote-dev/ainote-mcp'

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