Skip to main content
Glama
akhilkannur

Salestools Club

by akhilkannur

list_categories

Retrieves all sales tool categories with descriptions and tool counts from the Salestools Club registry.

Instructions

List all available sales tool categories with descriptions and tool counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_categories tool logic. It fetches categories from the API and formats them with name, tool count, and description.
    async function handleListCategories() {
      try {
        const data = await fetchJSON(`${BASE_URL}/api/categories`);
        let text = `# Sales Tool Categories\n\n`;
        for (const cat of data.categories) {
          text += `- **${cat.name}** — ${cat.toolCount} tools\n`;
          text += `  ${cat.description}\n\n`;
        }
        return { content: [{ type: "text", text: text.trim() }] };
      } catch (error) {
        return { content: [{ type: "text", text: `Failed to fetch categories: ${error.message}` }] };
      }
    }
  • The tool schema definition for list_categories, registered in the ListToolsRequestSchema handler. It has no required parameters.
    {
      name: "list_categories",
      description: "List all available sales tool categories with descriptions and tool counts.",
      inputSchema: { type: "object", properties: {} },
  • index.js:311-311 (registration)
    The routing/case statement in the CallToolRequestSchema handler that dispatches 'list_categories' to handleListCategories().
    case "list_categories": return handleListCategories();
Behavior2/5

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

No annotations provided, so description must fully convey behavior. Only states 'list all', implying a read operation, but no mention of authorization requirements, rate limits, or any side effects. Minimal disclosure.

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?

Single sentence, front-loaded with key action and details. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter list tool, the description adequately covers what is returned (categories, descriptions, counts). Complete given the tool's simplicity.

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?

Input schema has zero parameters (100% coverage). Description adds no parameter info, but none is needed. Baseline for 0-param tools is 4.

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?

Description specifies verb 'list', resource 'sales tool categories', and includes details 'with descriptions and tool counts'. Clearly distinguishes from sibling tools like search_sales_tools and get_tool_details.

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?

No explicit guidance on when to use this tool vs alternatives like search_sales_tools. Usage is implied as a simple overview, but lacks when-not-to-use or alternative suggestions.

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/akhilkannur/salestools-mcp'

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