Skip to main content
Glama
Sign In
qa-mcp

qa-mcp

by davidpoza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generateE2ETests

Automates the generation of end-to-end Cypress tests at a specified path, enabling QA teams to efficiently create test suites.

Instructions

Genera tests E2E Cypress en la ruta configurada.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generateE2ETests"
  }
}

Input Schema

NameRequiredDescriptionDefault
configPathNo
promptOverrideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations exist, and the description does not disclose any behavioral traits such as side effects (e.g., file creation), required authentication, or return value. This is a critical gap for a tool that likely modifies the file system.

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

Conciseness2/5

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

The description is very brief (1 line in Spanish) but omits essential information. It front-loads the purpose but is not adequately informative for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and two undocumented parameters, the description is severely incomplete. It does not cover return values, side effects, or parameter details, leaving the agent with insufficient context to use the tool correctly.

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

Parameters1/5

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

With 0% schema description coverage, the description fails to explain what configPath or promptOverride mean. It only mentions 'in the configured path,' which vaguely hints at configPath but provides no concrete semantics.

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 it generates E2E Cypress tests in the configured path, using a specific verb and resource. It implicitly distinguishes from the sibling tool 'generateRestTests' by focusing on E2E Cypress, but does not explicitly contrast them.

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?

No guidance is provided on when to use this tool versus alternatives like generateRestTests, nor are there any prerequisites or context for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools