Skip to main content
Glama

QualityKit verify

qualitykit.verify

Re-audit a Next.js repo after fixes or proposed files to verify finding IDs and opportunity route presence, returning readyToShip and recording applied or shipped status with Pro credentials.

Instructions

Re-audit after changes or against proposedFiles. Checks finding IDs and optional opportunityIds (route presence). Returns readyToShip; with Pro credentials, records mark_applied / shipped.

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": {
      "projectRoot": "<projectRoot>"
    },
    "name": "qualitykit.verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsNoOptional map of opportunityId → path when grow lookup is unavailable
apiKeyNo
siteUrlNo
apiBaseUrlNo
findingIdsNoLimit finding verification to these finding IDs
markAppliedNoWhen true (default) and Pro credentials are set, snapshot readyToShip ids via visibility.mark_applied
projectRootYesAbsolute path to the website repository root
proposedFilesNoProposed file contents to verify as if applied (not written)
opportunityIdsNoGrow/GSC page opportunity ids to check for route presence (page-*). Present ids are readyToShip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose two meaningful traits: verification happens without writing proposedFiles, and state recording (mark_applied/shipped) only occurs with Pro credentials. It leaves out whether verification itself mutates anything, what happens on partial failure, and any cost or rate considerations.

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?

Three short sentences, front-loaded with the primary use case, and no filler. The clipped telegraphic style ("Pro credentials", "records mark_applied / shipped") borders on cryptic but stays compact.

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?

For a 9-parameter tool with nested objects, no annotations, and no output schema, the description does the minimum: it names the headline return value (readyToShip) and one credential-gated side effect. It omits the rest of the response shape, credential acquisition, and error behavior, leaving genuine gaps for a tool of this complexity.

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 coverage is 67% across 9 parameters, so the schema handles much of the burden. The description adds real semantics only for opportunityIds (route-presence check, present ids become readyToShip) and proposedFiles (verified as-if-applied); it says nothing about paths, apiKey, siteUrl, apiBaseUrl, or projectRoot.

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?

The description uses specific verbs ("Re-audit", "Checks finding IDs", "Returns readyToShip") against a clearly scoped resource. It conveys the re-verification role well enough to separate it from a first-pass audit, though it never names qualitykit.audit or qualitykit.fix as the contrasting siblings.

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

Usage Guidelines3/5

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

"Re-audit after changes or against proposedFiles" gives a usable trigger condition for invoking the tool. However, there is no explicit when-not guidance, no mention of an initial-audit alternative, and no indication of prerequisites such as Pro credentials being required for the state-recording path.

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