Skip to main content
Glama

BRAINIAC Prevailing Wage

Build payroll report files

prevailing-wage_payroll-report

Generate an editable XLSX and a minimal PDF summary after DBRA precheck. Output is not a prescribed government form. Price $0.08 USDC. POST /api/v1/prevailing-wage/payroll-report. Unpaid calls return 402 and do not run.

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": {
      "wdId": "<wdId>",
      "weekEnding": "<weekEnding>",
      "cwhssaCovered": "<cwhssaCovered>",
      "project": "<project>",
      "workers": "<workers>"
    },
    "name": "prevailing-wage_payroll-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
wdIdYes
projectYes
workersYes
weekEndingYes
cwhssaCoveredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a fair job: it discloses the paid nature ($0.08 USDC), the exact failure mode ('Unpaid calls return 402 and do not run'), and the output artifacts including that the XLSX is editable. Gaps remain on whether files are returned inline vs. as links, and whether any record is persisted server-side.

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?

Four short sentences, telegraphic and front-loaded: output, then caveat, then price, then endpoint and payment behavior. Nothing is padded, though the price/endpoint details could arguably be consolidated into one line.

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?

The schema is genuinely complex (nested workers with seven required day entries, bounds, enums) and there is no output schema or annotation to lean on. The description covers commercial and failure behavior well but leaves the input contract almost entirely to the schema, which only describes two nested fields.

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?

All five required parameters — wdId, weekEnding, cwhssaCovered, project, and the nested workers array — are undocumented in the description, and schema description coverage is reported at 0% for the top level. For a tool whose core complexity is the nested worker/day structure, the description explains none of what these inputs mean or require.

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?

States a specific verb and deliverable set: 'Generate an editable XLSX and a minimal PDF summary'. Naming the two output formats plus the 'not a prescribed government form' caveat makes the intent unambiguous and distinct from the precheck sibling it references.

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?

'After DBRA precheck' establishes an ordering prerequisite and implicitly routes the agent to prevailing-wage_payroll-precheck, which is useful. However, it never states whether precheck is mandatory, what to do if it fails, or how this differs from the conformance-draft sibling — the guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources