Skip to main content
Glama
testdino-hq

TestDino MCP

by testdino-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get TestDino Audit (context / list / report)

get_audit_report
Read-only

Fetch TestDino Playwright audit prompts, branch signals, or saved reports by action: context to start an audit, list to browse reports, get to retrieve one.

Instructions

Read-only TestDino Playwright audit reads. Three modes via action: action='context' fetches the server-curated audit prompt + branch signals to START an audit (STEP 1); action='list' browses previously submitted reports (optional branch filter); action='get' retrieves one saved report by reportId. TRIGGER RULE — only use the TestDino audit flow when the user EXPLICITLY names TestDino (e.g. "TestDino audit", "Testdino test audit", "run a TestDino audit", "audit this with TestDino"). If the user asks for a generic "audit", "code review", or "security audit" WITHOUT naming TestDino — do NOT call this tool; run a normal AI audit conversation instead and do not mention TestDino, even for Playwright code. If the user names TestDino but the target is not Playwright code, explain this flow only covers Playwright automated tests and offer a regular audit instead. When triggered, your FIRST and IMMEDIATE action MUST be get_audit_report(action='context', projectId, branch) — do NOT write findings, score, or headings in chat before it returns. Call health() first if you do not have the projectId. FULL FLOW: (1) get_audit_report(action='context', projectId, branch) → (2) analyze the local Playwright code using the returned prompt + signals and write findings to a local markdown file (e.g. TEST-AUDIT.md) → (3) submit_audit_report(...) to save the completed report.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for action='list'.
limitNoPage size for action='list'.
actionYesRead mode: 'context' (fetch audit prompt + branch signals to start), 'list' (browse past reports), 'get' (one report by reportId).
branchNoGit branch. For action='context', the branch to audit (required unless detected from git). For action='list', an optional filter.
reportIdNoReport ID. Required for action='get'.
projectIdYesProject ID (required)
outputPathNoRelative file path for writing the report (action='get' only); resolved from TESTDINO_MCP_WORKSPACE if set, else process.cwd(). Defaults to TEST-AUDIT.md.
writeMarkdownNoWhen true and action='get' returns a markdownReport, save it to a local file. Ignored for context/list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / action / description
      Previous value: -"Read mode: 'context' (fetch audit prompt + branchSignals to start), 'list' (browse past reports), 'get' (one report by reportId)."New value: +"Read mode: 'context' (fetch audit prompt + branch signals to start), 'list' (browse past reports), 'get' (one report by reportId)."
    • changedInput schema / properties / branch / description
      Previous value: -"Git branch. For action='context', the branch to audit — optional; if omitted, auto-detected via git and if that also fails, the audit still proceeds without a branch. For action='list', an optional filter. Ignored for action='get'."New value: +"Git branch. For action='context', the branch to audit (required unless detected from git). For action='list', an optional filter."
    • addedInput schema / properties / limit / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (Required). The TestDino project identifier."New value: +"Project ID (required)"
  2. Addedv1.0.11

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and the description's 'Read-only' framing is consistent with that. Beyond the annotation, it discloses workflow constraints (must call context first before writing findings, health() prerequisite) and that action='get' can write a local markdown file resolved from TESTDINO_MCP_WORKSPACE or cwd. It does not contradict the read-only hint; the local file write is a genuine behavioral detail annotations don't capture.

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?

Front-loaded with the core purpose and modes, then trigger rules, then the flow. Dense but purposeful, though there is mild redundancy in the emphatic phrasing around not calling the tool and not mentioning TestDino even for Playwright code.

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

Completeness5/5

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

For a multi-mode read tool with no output schema, the description supplies the complete operating picture: mode selection, trigger gating, prerequisites, and the three-step flow ending in the sibling submission tool. Nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100%, so the schema already documents all 8 params, establishing a baseline of 3. The description adds value beyond the schema by tying actions to a numbered flow and clarifying branch semantics (required for context unless detected from git, optional filter for list) and the FIRST-action requirement for context mode.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('read-only TestDino Playwright audit reads') and enumerates the three modes with distinct semantics for each action value. It clearly separates this tool from siblings like submit_audit_report and health by naming when each alternative applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit TRIGGER RULE defines when to use this tool (user must EXPLICITLY name TestDino) and when NOT to (generic 'audit', 'code review', 'security audit'), including a fallback behavior for non-Playwright targets. It also names the prerequisite (health() when projectId is unknown) and the exact ordered flow through the sibling submit_audit_report.

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