Skip to main content
Glama

Verify Work

verify_work

Validate completed work by running sanity, test, git diff, and architecture checks against a task, then produce a reality verification dossier.

Instructions

Perform deep sanity, test, git diff, and architecture checks against a task to output a reality verification dossier.

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": {
      "task_id": "<task_id>"
    },
    "name": "verify_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the entire burden of disclosure. It implies the tool executes tests and inspects git diffs, which means possible long runtime and side effects, but it never states whether it is read-only, how expensive/slow it is, whether it mutates the workspace, or what happens if tests fail. Only the output artifact is hinted at.

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?

A single tightly-packed sentence with zero filler, and the action is front-loaded. The compression is at the cost of readability ('deep sanity' is jargon), but no sentence is wasteful.

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

Completeness2/5

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

An output schema exists, so return values need not be described. However, for a tool that orchestrates test runs, diff analysis, and architecture checks, the description says nothing about scope, cost, failure behavior, or how task_id links to the task system — significant gaps for a verification entry point with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description mentions neither parameter. It does not explain that task_id corresponds to a task registered via add_task/create_task, nor that path is a workspace root defaulting to the current directory. Both parameters are undocumented in both places.

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 names a specific verb ('verify') and enumerates the check dimensions (sanity, test, git diff, architecture) plus the output artifact (a reality verification dossier). This is clearly distinguishable in substance from siblings like validate_architecture or git_diff, though it never explicitly says how it differs from verify_outcome or verify_requirements.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus the many adjacent verification tools (verify_outcome, verify_requirements, compare_work_to_prd, validate_architecture) or versus running git_diff/run_command directly. No prerequisites, no exclusions, no workflow placement — the agent must infer that this is a post-work aggregation step.

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