Damn Vulnerable MCP Server (DVMCP)

Overview Schema Source Related Servers Discussions Admin

hr.run_payroll_report

Generate payroll reports for specific pay periods, including compensation, tax withholdings, and direct deposit details. Filter results by department.

Instructions

Generate a payroll report for a given pay period. Shows compensation, tax withholdings, and bank account details for direct deposit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hr.run_payroll_report"
  }
}

Input Schema

Name	Required	Description	Default
`period`	No	Pay period (e.g., '2026-02')
`department`	No	Filter by department

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jun 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It reveals the report's content (compensation, tax withholdings, bank account details) and implies a read-only/computation operation. However, it does not mention access restrictions, side effects, or output format, which would be useful for a tool handling sensitive payroll data.

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 two sentences: the first states the purpose, the second briefly outlines the output contents. It is front-loaded, concise, and every sentence adds information without redundancy.

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 simple two-parameter tool with no output schema, the description covers the main purpose and output contents. However, it does not clarify behavior when optional parameters are omitted (e.g., period default) and does not mention the 'department' filter, leaving minor gaps. Overall, it is reasonably complete for its simplicity.

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 description coverage is 100%, with both parameters ('period' and 'department') documented. The description adds no additional parameter semantics beyond restating 'pay period' and omitting any mention of the 'department' filter. Thus, it provides no value beyond the schema, warranting the baseline score.

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 function: 'Generate a payroll report for a given pay period.' It uses a specific verb ('generate') and identifies the resource ('payroll report') and scope. It also distinguishes from sibling HR tools like employee search or offer letter generation.

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?

The description implies when to use the tool (generating a payroll report for a pay period) but does not explicitly state when not to use it or mention alternatives. It provides clear context but lacks exclusions or comparisons to sibling tools.

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