Skip to main content
Glama
watchdealer-pavel

WatchBase MCP Server

search_refnr

Find watches in the WatchBase database by entering a reference number, supporting partial matches for flexible searching.

Instructions

Search the database by reference number (allows partial matches).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch keywords (reference number)

Implementation Reference

  • Handler logic for the 'search_refnr' tool. Validates input arguments, sets API path to 'search/refnr', and query parameter to the provided 'q'.
    case 'search_refnr':
      if (!isSearchArgs(args)) throw new McpError(ErrorCode.InvalidParams, 'Invalid arguments for search_refnr');
      apiPath = 'search/refnr';
      apiParams = { q: args.q };
      break;
  • src/index.ts:109-120 (registration)
    Tool registration entry defining the name, description, and input schema for 'search_refnr'. This is part of the tools array returned by ListToolsRequestSchema handler.
    {
      name: 'search_refnr',
      description:
        'Search the database by reference number (allows partial matches).',
      inputSchema: {
        type: 'object',
        properties: {
          q: { type: 'string', description: 'Search keywords (reference number)' },
        },
        required: ['q'],
      },
    },
  • Type guard (schema validation) for input arguments of 'search_refnr' tool, ensuring args is an object with a string 'q' property.
    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 but only states the partial match capability. It doesn't disclose whether this is a read-only operation, what permissions are needed, how results are returned (format, pagination), or any rate limits. The description adds minimal behavioral context beyond the basic function.

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 with zero wasted words. It front-loads the core function and includes the key behavioral detail (partial matches) without 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 simple search tool with one parameter and no output schema, the description covers the basic purpose and partial match behavior adequately. However, with no annotations and no output schema, it lacks details on return format, error conditions, or operational constraints that would be helpful for an agent.

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 has 100% description coverage, with the parameter 'q' documented as 'Search keywords (reference number)'. The description adds that it allows partial matches, which provides useful context beyond the schema, but doesn't elaborate on syntax or format requirements. Baseline 3 is appropriate given high schema coverage.

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 action ('Search') and resource ('database by reference number'), with the specific capability of partial matches. It distinguishes from the generic 'search' sibling by specifying reference number searches, though it doesn't explicitly contrast with other siblings like list operations.

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 when searching by reference number with partial matching, but doesn't explicitly state when to use this tool versus the generic 'search' sibling or list operations. No guidance on prerequisites or exclusions is provided.

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