Skip to main content
Glama
watchdealer-pavel

WatchBase MCP Server

get_watch_details

Retrieve comprehensive watch metadata including technical specifications, reference numbers, and collection details by providing a watch ID.

Instructions

Retrieve the full details for a particular watch by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the watch

Implementation Reference

  • Specific handler logic for the 'get_watch_details' tool within the CallToolRequestSchema handler. Validates input using isGetWatchDetailsArgs, sets the API endpoint path to 'watch' and parameters to the provided watch ID, then proceeds to the shared API call execution.
    case 'get_watch_details':
      if (!isGetWatchDetailsArgs(args)) throw new McpError(ErrorCode.InvalidParams, 'Invalid arguments for get_watch_details');
      apiPath = 'watch';
      apiParams = { id: args.id };
      break;
  • JSON Schema definition for the input parameters of the 'get_watch_details' tool, specifying an object with a required 'id' field that can be string or number.
    inputSchema: {
      type: 'object',
      properties: {
        id: {
          oneOf: [{ type: 'string' }, { type: 'number' }],
          description: 'ID of the watch',
        },
      },
      required: ['id'],
    },
  • src/index.ts:165-178 (registration)
    Tool registration entry in the tools array returned by ListToolsRequestSchema handler. Includes name, description, and input schema for 'get_watch_details'.
    {
      name: 'get_watch_details',
      description: 'Retrieve the full details for a particular watch by its ID.',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            oneOf: [{ type: 'string' }, { type: 'number' }],
            description: 'ID of the watch',
          },
        },
        required: ['id'],
      },
    },
  • Type guard helper function used in the handler to validate that arguments match the expected shape: an object with 'id' as string or number.
    const isGetWatchDetailsArgs = (args: any): args is { id: string | number } =>
      typeof args === 'object' &&
      args !== null &&
      (typeof args.id === 'string' || typeof args.id === 'number');
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action ('Retrieve') but doesn't disclose behavioral traits like whether this is a read-only operation, error handling for invalid IDs, authentication needs, rate limits, or response format. This leaves significant gaps for a tool with no annotation support.

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 directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with zero waste, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'full details' include, error scenarios, or return values, which are crucial for a retrieval tool. With low contextual support from structured fields, the description should provide more completeness but fails to do so.

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 input schema has 100% description coverage, with the 'id' parameter documented as 'ID of the watch'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline of 3 where the 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 ('full details for a particular watch'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_watches' or 'search', which might also retrieve watch information but with different scopes or filters.

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 such as 'list_watches' or 'search'. It mentions retrieving details by ID, but doesn't clarify if this is for single-item lookups or when other tools might be more appropriate, leaving usage context implied at best.

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