Assert
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASSERT_API_KEY | Yes | Your Assert API key obtained from the Assert dashboard (dashboard.assert.click). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assert_listA | List existing E2E test scenarios saved in Assert. Use this to audit coverage before generating new tests. Supports filtering by project and pagination. |
| assert_generateA | Generate a ready-to-run E2E test scenario in Assert Markdown format from a plain-English description. Optionally save it to Assert for later execution. |
| assert_runA | Execute a test scenario and return a run ID. Accepts either a saved scenario_id or ad-hoc markdown. Runs are async — use assert_status to poll for completion. |
| assert_statusA | Poll a test run for its current status and step-level results. Returns pass/fail with actionable failure details and screenshot URLs for failed steps. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: generate creates tests, list retrieves existing ones, run executes tests, and status checks results. The descriptions explicitly differentiate their functions, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent 'assert_verb' pattern (assert_generate, assert_list, assert_run, assert_status), using snake_case and clear action verbs. This predictability enhances usability and reduces cognitive load for agents.
With 4 tools, the server is well-scoped for E2E test management, covering the full lifecycle: generate, list, run, and status check. Each tool earns its place without bloat, making the set efficient and focused on its domain.
The toolset provides complete CRUD-like coverage for E2E test scenarios: create (generate), read (list), execute (run), and monitor (status). There are no obvious gaps, as it supports both saved and ad-hoc tests with actionable feedback, enabling seamless agent workflows.