Skip to main content
Glama
watchdealer-pavel

WatchBase MCP Server

list_families

Retrieve all watch families for a specific brand to explore collections and models within the WatchBase database.

Instructions

Retrieve a list of all families for a given brand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brand_idYesBrandID of the brand

Implementation Reference

  • Handler logic for the 'list_families' tool: validates input arguments, sets the API endpoint to '/families' and maps 'brand_id' to 'brand-id' parameter.
    case 'list_families':
      if (!isListFamiliesArgs(args)) throw new McpError(ErrorCode.InvalidParams, 'Invalid arguments for list_families');
      apiPath = 'families';
      apiParams = { 'brand-id': args.brand_id }; // API uses hyphen
      break;
  • src/index.ts:127-139 (registration)
    Registration of the 'list_families' tool in the tools array, including name, description, and input schema definition.
      name: 'list_families',
      description: 'Retrieve a list of all families for a given brand.',
      inputSchema: {
        type: 'object',
        properties: {
          brand_id: {
            oneOf: [{ type: 'string' }, { type: 'number' }],
            description: 'BrandID of the brand',
          },
        },
        required: ['brand_id'],
      },
    },
  • Type guard function for validating 'list_families' tool arguments (schema validation helper).
    const isListFamiliesArgs = (args: any): args is { brand_id: string | number } =>
      typeof args === 'object' &&
      args !== null &&
      (typeof args.brand_id === 'string' || typeof args.brand_id === 'number');
  • Shared API execution and response formatting logic used by all tools, including 'list_families'.
    const response = await this.axiosInstance.get(apiPath, { params: apiParams });
    
    // Return successful response
    return {
      content: [
        {
          type: 'text', // Corrected type to 'text'
          text: JSON.stringify(response.data, null, 2), // JSON content is in the text field
        },
      ],
    };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation but doesn't mention whether it's paginated, rate-limited, requires authentication, returns structured data, or has any side effects. For a list operation with zero annotation coverage, this leaves significant 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 communicates the core purpose without any wasted words. It's appropriately sized for a simple list operation and front-loads the essential information.

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 tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what a 'family' represents in this domain, what format the returned list takes, or how this tool relates to sibling tools like 'list_watches'. The agent would need to guess about important contextual 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?

The schema description coverage is 100%, with the single parameter 'brand_id' clearly documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline score when schema does the heavy lifting.

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 ('Retrieve') and resource ('list of all families for a given brand'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its sibling 'list_brands' or 'list_watches', which would be needed for a perfect score.

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 'list_brands' or 'list_watches'. It mentions the required 'brand_id' parameter but doesn't explain the relationship between brands, families, and watches, leaving the agent to infer usage context.

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/watchdealer-pavel/watchbase-mcp-server'

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