Skip to main content
Glama

submit_audit_report

Submit a completed audit report to TestDino, including score, findings, and recommendations, so it is stored and attached to the correct audit 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. Every finding MUST include title, summary, and severity (low|medium|high|critical) — incomplete findings are rejected, not stored. target, if sent, accepts only { value, path }. 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.
targetNoOptional scoped-audit target. Only { value, path } (non-empty strings) are stored — the dashboard reads these; any other key is rejected.
findingsNoArray of findings. Each finding REQUIRES title, summary, and severity (critical/high/medium/low) — a finding missing any of these is rejected, not stored. 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, recommendation, and evidence (file, lineStart, lineEnd, observation).
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.
Behavior4/5

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

With no annotations, the description carries the disclosure burden; it reveals that write permission is required, incomplete findings are rejected and not stored, target only accepts {value, path}, and matching the audit context matters. It does not describe the response/error format or side effects of writeMarkdown, but the core mutation and validation behaviors are transparent.

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 long but front-loaded with 'FINAL STEP' and every sentence contributes operational value. It is dense and slightly repetitive around required fields, but given 13 parameters and zero annotations, the length is justified.

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 complex final-step mutation with no output schema, the description covers flow prerequisites, validation rules, orgId resolution, and reuse of context identifiers. It does not describe the return value or post-submission behavior, but the operational context is well covered overall.

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?

The schema already covers all 13 parameters, but the description adds valuable cross-parameter constraints: score plus markdownReport/markdownReportPath are required, findings must include title/summary/severity, and target is restricted to {value, path}. It slightly conflicts with the schema's required array (which lists only projectId, orgId, score), preventing full credit.

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 opens with 'FINAL STEP of the TestDino Playwright audit flow — submits a completed audit report,' giving a specific verb and resource and clearly distinguishing it from siblings like get_audit_report. It unambiguously communicates that this tool writes/submits a report rather than reading or querying data.

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?

It explicitly states 'Call this only AFTER get_audit_report(action='context') and after you have analyzed the local Playwright code and produced findings,' defining the exact prerequisite sequence. It also provides actionable guidance on resolving orgId via health() and reusing the same branch/scope/target from the context call.

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