Skip to main content
Glama
watchdealer-pavel

WatchBase MCP Server

search

Find watches in the WatchBase database by entering brand, family, model names, or reference numbers. This tool helps users locate specific watch information using targeted search queries.

Instructions

Search the database by brand name, family name, watch name and reference number (whole words).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch keywords

Implementation Reference

  • The handler function for the 'search' tool within the CallToolRequestSchema request handler. It validates the input arguments using the isSearchArgs type guard and sets the apiPath and apiParams for the subsequent API call to 'search' endpoint.
    case 'search':
      if (!isSearchArgs(args)) throw new McpError(ErrorCode.InvalidParams, 'Invalid arguments for search');
      apiPath = 'search';
      apiParams = { q: args.q };
      break;
  • src/index.ts:97-108 (registration)
    Registers the 'search' tool in the tools array used by the ListToolsRequestSchema handler.
    {
      name: 'search',
      description:
        'Search the database by brand name, family name, watch name and reference number (whole words).',
      inputSchema: {
        type: 'object',
        properties: {
          q: { type: 'string', description: 'Search keywords' },
        },
        required: ['q'],
      },
    },
  • Input schema definition for the 'search' tool, specifying the required 'q' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        q: { type: 'string', description: 'Search keywords' },
      },
      required: ['q'],
    },
  • Type guard helper function used to validate arguments for the 'search' tool (shared with 'search_refnr').
    const isSearchArgs = (args: any): args is { q: string } =>
      typeof args === 'object' && args !== null && typeof args.q === 'string';
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 mentions 'whole words' matching, which is useful context beyond the schema. However, it doesn't describe other important behaviors like pagination, result format, error handling, or performance characteristics, leaving significant gaps for a search tool.

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 clearly states the purpose and key constraint ('whole words'). Every word earns its place with no redundancy or unnecessary elaboration.

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?

For a search tool with 1 parameter (100% schema coverage) but no annotations and no output schema, the description provides adequate basic information about search fields and matching behavior. However, it lacks details about result structure, limitations, or error cases that would be helpful given the absence of 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?

Schema description coverage is 100%, so the schema already documents the 'q' parameter as 'Search keywords'. The description adds value by specifying what fields are searched (brand name, family name, watch name, reference number) and the 'whole words' matching behavior, but doesn't provide additional syntax or format details beyond what the schema implies.

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 tool searches a database using specific fields (brand name, family name, watch name, reference number) and specifies 'whole words' matching. It distinguishes from siblings like 'list_brands' or 'get_watch_details' by being a general search, though it doesn't explicitly differentiate from 'search_refnr' which appears to be a more specialized search tool.

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?

The description implies usage for searching by specific fields with whole-word matching, but doesn't explicitly state when to use this tool versus alternatives like 'search_refnr' or 'list_watches'. It provides some context (searching by multiple fields) but lacks clear exclusions or named alternatives.

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