Skip to main content
Glama
jasonlcs

Waferlock Robot MCP

by jasonlcs

get_manual_info

Retrieve detailed information about specific robot manuals using their file ID to access technical documentation and operational guides.

Instructions

Get information about a specific manual by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileIdYesThe ID of the manual file

Implementation Reference

  • The core handler function that implements the get_manual_info tool. It fetches the manual by ID using the manualProvider, returns a not-found message if absent, otherwise serializes the manual for structured content and formats it for text response.
    async (args) => {
      const manual = await this.manualProvider.getManualById(args.manualId);
      if (!manual) {
        return {
          content: [
            {
              type: 'text',
              text: `Manual ${args.manualId} not found.`,
            },
          ],
        };
      }
      const serialised = serialiseManual(manual);
      return {
        content: [
          {
            type: 'text',
            text: formatManual(manual),
          },
        ],
        structuredContent: serialised,
      };
    }
  • The input schema and description for the get_manual_info tool, using Zod for validating the required manualId string parameter.
    {
      description: 'Get basic information about a specific manual (metadata only, no content/download)',
      inputSchema: { manualId: z.string() },
    },
  • The registration of the get_manual_info tool on the MCP server, including name, schema, and inline handler function.
    this.server.registerTool(
      'get_manual_info',
      {
        description: 'Get basic information about a specific manual (metadata only, no content/download)',
        inputSchema: { manualId: z.string() },
      },
      async (args) => {
        const manual = await this.manualProvider.getManualById(args.manualId);
        if (!manual) {
          return {
            content: [
              {
                type: 'text',
                text: `Manual ${args.manualId} not found.`,
              },
            ],
          };
        }
        const serialised = serialiseManual(manual);
        return {
          content: [
            {
              type: 'text',
              text: formatManual(manual),
            },
          ],
          structuredContent: serialised,
        };
      }
    );
  • Helper function to serialize a manual object for structured output, handling date serialization and optional fields.
    function serialiseManual(manual: UploadedFile) {
      return {
        ...manual,
        uploadedAt: manual.uploadedAt instanceof Date ? manual.uploadedAt.toISOString() : manual.uploadedAt,
        indexStartedAt: manual.indexStartedAt || null,
        indexCompletedAt: manual.indexCompletedAt || null,
      };
    }
  • Helper function to format a single manual as a pretty-printed JSON string for text content.
    function formatManual(manual: UploadedFile): string {
      return JSON.stringify(serialiseManual(manual), null, 2);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't specify aspects like authentication needs, rate limits, error handling, or what 'information' includes (e.g., metadata, content). This is a significant gap for a tool with zero annotation coverage.

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 any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate but has clear gaps. It lacks details on behavioral traits and usage context, which are important for an agent to operate effectively, though the simple schema reduces the need for extensive explanation.

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 'fileId' clearly documented in the schema. The description adds no additional meaning beyond what the schema provides, 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 action ('Get information') and resource ('about a specific manual by ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_manuals' or 'search_manuals' beyond the 'by ID' specificity, which is why it doesn't reach a 5.

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_manuals' or 'search_manuals'. It implies usage for retrieving info by ID but lacks explicit context, prerequisites, or exclusions, leaving the agent to infer when this is appropriate.

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/jasonlcs/waferlock-robot-mcp-public'

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