Skip to main content
Glama

Show TestDino Audit Scorecard

show_audit_report
Read-only

Show a saved Playwright audit as a scorecard with score band, lost points, top issues, and a full-report link. Use it to view or summarize a specific audit report or the latest one on a branch.

Instructions

Read-only. Shows a saved TestDino Playwright audit as a scorecard: the score and its band (Strong, Fair, Needs work, At risk), where the points were lost, the top issues, and a link to the full report. Use when the user asks to see, show or summarize an audit report. Pass reportId for a specific report; omit it for the latest one, optionally on a branch.

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>"
    },
    "name": "show_audit_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoBranch to take the latest report from when reportId is omitted.
reportIdNoAudit report ID. Omit for the latest report.
projectIdYesProject ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the leading 'Read-only.' largely restates them. What the description adds beyond the schema is the fallback resolution behavior (no reportId means the latest report) and the summary nature of the output. With no output schema, more could be said about size or fidelity of the scorecard versus the full report, but the safety profile is fully covered by annotations.

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 safety marker, then purpose, then returned contents, then usage — a sensible order. Some waste in the synonym triple 'see, show or summarize' and in restating the read-only annotation, but nothing extraneous beyond that.

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

Completeness4/5

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

For a three-parameter, read-only lookup with no output schema, the description covers what the result contains, which parameter selects a specific report, and what happens by default. The main residual gap is how this differs from the sibling get_audit_report, which matters for selection.

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% and the schema already states 'Omit for the latest report' and 'Branch to take the latest report from when reportId is omitted.' The description restates the same semantics rather than adding new meaning, only reiterating that branch is conditional on omitting reportId. Baseline 3 applies because structured fields do the work.

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?

Specific verb plus resource with enumerated contents: 'Shows a saved TestDino Playwright audit as a scorecard: the score and its band... where the points were lost, the top issues, and a link to the full report.' An agent can picture the output. It stops short of naming the sibling get_audit_report, so the boundary between 'show scorecard' and 'get report' is left to inference.

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

Usage Guidelines4/5

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

Explicit trigger is given ('Use when the user asks to see, show or summarize an audit report') plus parameter-selection rules: pass reportId for a specific report, omit for the latest, optionally on a branch. It does not say when to prefer a different tool such as get_audit_report or submit_audit_report, so no exclusions are stated.

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