Skip to main content
Glama
lucad87

MCP Server - Test Migration (WDIO to Playwright)

by lucad87

get_playwright_docs

Retrieve Playwright documentation for specific features to understand migration patterns when converting WebDriverIO tests to Playwright.

Instructions

Retrieves relevant Playwright documentation for specific features, commands, or concepts. Useful for understanding migration patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesThe Playwright feature or concept to get documentation for (e.g., "selectors", "assertions", "fixtures", "page-object-model")

Implementation Reference

  • The handler function that executes the 'get_playwright_docs' tool by invoking the `getPlaywrightDocs` utility.
    export async function handleGetPlaywrightDocs(args) {
      const { topic } = args;
      const docs = getPlaywrightDocs(topic);
    
      return {
        content: [{
          type: 'text',
          text: docs,
        }],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full disclosure burden. While 'Retrieves' implies a read-only operation, the description fails to specify output format (markdown, plain text, structured JSON?), whether results are cached, or any rate limiting concerns. It does not disclose what 'relevant' means algorithmically.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description consists of two efficient sentences totaling 12 words. The primary action is front-loaded in the first sentence, and the second sentence provides contextual usage hints. No redundant or filler text is present, though the second sentence could be more specific.

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?

With no output schema provided, the description should ideally describe the return format (documentation text, code examples, links?). It fails to do so. For a single-parameter retrieval tool, the description covers the input side but leaves the output side completely undocumented.

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% coverage with the 'topic' parameter fully described including examples. The description mentions 'specific features, commands, or concepts' which aligns with the schema but adds no additional semantic value beyond what the schema already provides. Baseline 3 is appropriate given comprehensive 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 tool 'Retrieves relevant Playwright documentation' using a specific verb and resource. However, it does not explicitly differentiate from siblings like 'migrate_to_playwright' or 'compare_frameworks' beyond implicitly mentioning the 'migration' context.

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 mentions the tool is 'Useful for understanding migration patterns,' which provides implied context, but lacks explicit guidance on when to use this versus alternatives (e.g., when to lookup docs vs. when to run the actual migration). No 'when-not' or alternative recommendations are 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/lucad87/mcp-server-tests-migration'

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