Skip to main content
Glama

Get TestDino Audit (context / list / report)

get_audit_report
Read-only

Starts a TestDino Playwright audit with checklist and run signals, lists previously submitted reports, or retrieves a saved report by ID for review.

Instructions

Read-only TestDino Playwright audit reads. Three modes via action: action='context' returns TestDino's audit checklist (what to check, the finding format and severity levels) plus this branch's run signals, CI suggestions and the last audit's findings, 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 against the returned checklist and signals and write findings to a local markdown file (e.g. TEST-AUDIT.md) → (3) show the user the findings and ask whether to save the audit to TestDino, which is when the score is computed; call submit_audit_report on a yes, or straight away if they explicitly asked to save it (asking for an audit is not asking to save it).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "action": "<action>"
    },
    "name": "get_audit_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for action='list'.
limitNoPage size for action='list'.
actionYesRead mode: 'context' (audit checklist + 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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Read mode: 'context' (fetch audit prompt + branch signals to start), 'list' (browse past reports), 'get' (one report by reportId)."New value: +"Read mode: 'context' (audit checklist + branch signals to start), 'list' (browse past reports), 'get' (one report by reportId)."
    • removedInput schema / properties / outputPath
      Removed value: -{
      -  "description": "Relative file path for writing the report (action='get' only); resolved from TESTDINO_MCP_WORKSPACE if set, else process.cwd(). Defaults to TEST-AUDIT.md.",
      -  "type": "string"
      -}
    • removedInput schema / properties / writeMarkdown
      Removed value: -{
      -  "description": "When true and action='get' returns a markdownReport, save it to a local file. Ignored for context/list.",
      -  "type": "boolean"
      -}
  2. 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)"
  3. Addedv1.0.11

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint=false/destructiveHint=false, yet the description still adds substantial behavioral context: what 'context' returns, that the score is only computed at submit time, that nothing should be written to chat before context returns, and the Playwright-only scope limitation. This is well beyond what the annotations convey.

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?

Dense but front-loaded: identity, then mode breakdown, then trigger rule, then mandated first call, then full flow. The four-part structure is easy to scan; the FULL FLOW section partially restates the mode descriptions, which is the only real redundancy.

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 tool with no output schema, the description covers entry conditions, the mandatory first call, what context returns, the analysis/save handoff, and the exact confirmation gate before submit. An agent has everything needed to sequence calls correctly.

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?

Schema description coverage is 100%, so every parameter including the action enum, branch, reportId, page and limit is already documented in the schema. The description reinforces mode semantics but adds no new syntax, defaults, or format detail for branch detection, pagination, or reportId shape.

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?

Opens with a specific verb+resource ("Read-only TestDino Playwright audit reads") and decomposes the tool into three named modes with distinct outcomes (context = checklist + branch signals, list = browse past reports, get = one report by reportId). This cleanly separates it from siblings like submit_audit_report and show_audit_report.

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?

Provides an explicit TRIGGER RULE with when-to-use, when-NOT-to-use (generic "audit", "code review", "security audit" without naming TestDino), and the alternative behavior to take instead. It also states the prerequisite for health() when projectId is missing and hands off to submit_audit_report at the correct step.

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