Cypress Page Object Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_page_objectD | – |
| modify_page_objectD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have distinct verbs (generate vs modify) targeting the same resource (page object), so an agent can differentiate between creating a new page object and altering an existing one. However, with no descriptions, the exact scope and input requirements of each tool remain unclear, creating minor uncertainty.
Both tools follow a consistent verb_noun pattern (generate_page_object, modify_page_object), using clean snake_case with no deviations. The naming is fully predictable and readable.
Two tools are a bit thin for a generator that might also need to list, delete, or validate page objects, but for a focused create-and-modify utility the count is reasonable. It is not an extreme mismatch, just slightly under-scoped.
The domain appears to be page object lifecycle: generate and modify are covered, but there is no tool to get, list, delete, or validate page objects. Notable gaps exist, though an agent could work through generate and modify for basic workflows.