Skip to main content
Glama

submit_audit_report

Submit the completed Playwright audit report with score, findings, and recommendations to finalize the audit flow and attach it to the correct context.

Instructions

FINAL STEP of the TestDino Playwright audit flow — submits a completed audit report. Requires write permission. Call this only AFTER get_audit_report(action='context') and after you have analyzed the local Playwright code and produced findings. score (0-100) and either markdownReport or markdownReportPath are required. Include findings, recommendations, reportName, branch, scope, and target as available. orgId is required — resolve it via health() if you do not already have it. Use the same branch/scope/target you passed to get_audit_report(action='context') so the report attaches to the right audit context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesOrganization ID (Required to submit). Resolve via health() if you don't have it.
scopeNoAudit scope. Defaults to 'suite'. Use 'feature' or 'spec_file' when the user names a slice such as auth/login, dashboards, or a specific spec.
scoreYesFinal audit score (0-100). Required.
branchNoGit branch that was audited. Optional — auto-detected via git if omitted.
targetNoStructured audit target (e.g. spec path, feature area). Pass this when the audit was scoped to a specific slice.
findingsNoArray of findings. Each should have: title, category, severity (critical/high/medium/low), summary, recommendation, and evidence (file, lineStart, lineEnd, observation). category must be one of: surface_level_tests, missing_validation, stability_issues, hard_to_maintain, coverage_gaps, organization_ownership, setup_configuration, duplication_overlap, other. Optional: subCategory.
projectIdYesProject ID (Required). The TestDino project identifier.
outputPathNoRelative file path for the local save (see writeMarkdown). Resolved from TESTDINO_MCP_WORKSPACE. Defaults to TEST-AUDIT.md.
reportNameNoShort human-readable title for the saved report (e.g. 'Login Flow Tests', 'API Integration Suite').
writeMarkdownNoWhen true, also write the submitted markdown to a local file. Ignored when markdownReportPath was supplied (the file already exists on disk).
markdownReportNoThe complete markdown report content. Prefer markdownReportPath to avoid large tool calls.
recommendationsNoArray of recommendation strings.
markdownReportPathNoPath to a local markdown file to read for submission. Relative from TESTDINO_MCP_WORKSPACE (or an absolute path). Preferred over markdownReport.
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses that write permission is required and that writeMarkdown triggers local file saving. However, it does not describe the submission outcome, side effects, or error states. For a tool with no annotations, more behavioral context would be beneficial.

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?

The description is a single dense paragraph that packs essential information without fluff. It could be broken into logical sections for readability, but there is no wasted text. Given the complexity (13 parameters), it strikes a reasonable balance between completeness and conciseness.

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

Completeness3/5

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

The description covers the workflow context well (order of operations, required parameters, parameter relationships). However, it lacks any mention of return values or response format, and the tool has no output schema. For a complex mutation tool with nested objects, clarifying what the agent can expect after submission would improve completeness.

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 coverage is 100%, establishing a baseline of 3. The description goes beyond by explaining that markdownReportPath is preferred to avoid large calls, that scope defaults to 'suite' and provides guidance on when to use other enum values, and that branch auto-detects. This adds meaningful context that helps the agent choose correct parameter values.

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?

The description clearly states the tool's role as the 'FINAL STEP of the TestDino Playwright audit flow' and specifies the action 'submits a completed audit report'. This verb+resource combination distinguishes it from sibling tools, which focus on creation, retrieval, or update of other entities.

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?

The description explicitly guides the agent to call this tool only after get_audit_report and analysis, and provides instructions on required parameters (score and either markdownReport or markdownReportPath) and consistency of branch/scope/target. It also mentions resolving orgId via health(). While it doesn't state when not to use it, the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/testdino-hq/testdino-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server