Skip to main content
Glama
Sign In
deepwork

deepwork

by saisharan0103
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Run a constrained verification command

run_verification
Destructive

Run a planned check command, fingerprinting the workspace before and after to detect disruptive mutations that invalidate verification. Alternatively, record evidence that no tests apply.

Instructions

Execute one planned test/lint/check/build command from the untrusted repository without a shell, fingerprinting the workspace before and after. Repository-controlled code can spawn processes, access the network, or destructively mutate files; a detected mutation makes verification fail. Alternatively, record specific evidence that no executable tests apply.

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": {
      "taskId": "<taskId>"
    },
    "name": "run_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes
commandNo
timeoutMsNo
noTestsEvidenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

The description goes beyond annotations by detailing fingerprinting behavior, potential for spawning processes, network access, and destructive file mutations. It clearly states that detected mutations cause verification failure, adding significant behavioral context not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two sentences. The first sentence front-loads the primary action and security context; the second covers the alternative. No redundant or unnecessary information.

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?

Given the tool's complexity (destructive, open-world), annotations, and lack of output schema, the description covers the core concept and security implications but lacks detail on remaining parameters and return behavior. It is minimally adequate but leaves gaps for an agent to fully understand usage without additional context.

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?

With 0% schema description coverage, the description must compensate but only partially. It implies the 'command' parameter for the action and 'noTestsEvidence' for the alternative, but does not explain 'taskId' or 'timeoutMs', nor their constraints. The meaning added is minimal and incomplete.

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 it executes a planned test/lint/check/build command, with a specific verb and resource. It distinguishes itself from sibling tools by focusing on execution and includes an alternative action for no-test evidence.

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 provides clear context for when to use this tool (for running verification commands from an untrusted repository) and mentions an alternative within the tool (recording no-test evidence). However, it does not explicitly compare to sibling tools like inspect_repository or final_gate, so usage guidance is good but not exhaustive.

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

Deploy Server

Other Tools