Skip to main content
Glama
jasonlcs

Waferlock Robot MCP

by jasonlcs

list_manuals

Access and browse all available Waferlock product manuals to find specific documentation for robot management and operation.

Instructions

List all uploaded Waferlock product manuals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'list_manuals' MCP tool, including description, empty input schema, and inline handler function that fetches the list of manuals via the manualProvider, serializes them, formats a text response, and provides structured content.
    this.server.registerTool(
      'list_manuals',
      { 
        description: 'List all available manuals with basic metadata (no download)',
        inputSchema: {}
      },
      async () => {
        const manuals = await this.manualProvider.listManuals();
        const serialised = manuals.map(serialiseManual);
    
        return {
          content: [
            {
              type: 'text',
              text:
                serialised.length > 0
                  ? `Found ${serialised.length} manuals:\n\n${formatManualList(manuals)}`
                  : 'No manuals found.',
            },
          ],
          structuredContent: {
            manuals: serialised,
          },
        };
      }
    );
  • The core handler logic for listing manuals: makes an authenticated API request to '/api/files/list', parses the ListResponse, and maps API manuals to UploadedFile objects.
    async listManuals(): Promise<UploadedFile[]> {
      const data = await request<ListResponse>('/api/files/list');
      return (data.files || []).map(toUploadedFile);
    },
  • Helper function to serialize UploadedFile objects for JSON output, ensuring dates are strings and optional fields are null if missing.
    function serialiseManual(manual: UploadedFile) {
      return {
        ...manual,
        uploadedAt: manual.uploadedAt instanceof Date ? manual.uploadedAt.toISOString() : manual.uploadedAt,
        indexStartedAt: manual.indexStartedAt || null,
        indexCompletedAt: manual.indexCompletedAt || null,
      };
  • Type definition for the API response from /api/files/list, defining the structure of the manuals list.
    interface ListResponse {
      files: ApiManual[];
    }
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 it lists manuals but doesn't describe return format, pagination, sorting, or any constraints (e.g., permissions, rate limits). For a tool with zero annotation coverage, this is a significant gap in transparency.

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 waste. It's front-loaded with the core action and resource, making it easy to parse and appropriately sized for the tool's simplicity.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, fields), behavioral traits, or how it differs from siblings. For a tool with no structured data support, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, but with no parameters, this is acceptable, and it doesn't need to compensate for any gaps.

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 ('List') and resource ('uploaded Waferlock product manuals'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'search_manuals' or 'get_manual_info', which prevents 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 'search_manuals' or 'get_manual_info'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent without direction on tool selection.

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