Skip to main content
Glama

BRAINIAC Prevailing Wage

Validate a labor classification

prevailing-wage_classification-validate

Use deterministic keyword matching against a selected wage determination. Ambiguous work is routed for human conformance review. Price $0.02 USDC. POST /api/v1/prevailing-wage/classification-validate. 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>",
      "duties": "<duties>"
    },
    "name": "prevailing-wage_classification-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
wdIdYes
tradeNo
dutiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden, and it does add real value: deterministic matching, human-review escalation for ambiguous input, a $0.02 USDC price, and a 402 failure mode where unpaid calls do not execute. It still omits what qualifies as ambiguous, whether the call is idempotent or persists anything, and any auth/payment prerequisites beyond the 402 hint.

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 with no filler; the payment and failure conditions are stated plainly. It leads with mechanism rather than purpose, but nothing is padded or redundant.

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?

For a tool with zero annotation coverage, 0% parameter documentation, and no output schema, the description should explain what a successful response looks like (verdict, matched classification, confidence) and what the caller must supply. Those gaps are material for a paid, mutating-by-method POST endpoint.

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% across three parameters, so the description should compensate but largely does not. 'A selected wage determination' loosely maps to wdId and 'ambiguous work' hints at duties, but the trade parameter is never mentioned and no format, length, or expected value guidance is added for any field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the mechanism (deterministic keyword matching against a selected wage determination) and the tool name says 'validate', but it never states the outcome being produced — e.g. whether a trade/duties pair is confirmed, rejected, or flagged. It also does not distinguish this from the sibling classification-rates tool, leaving the agent to infer the boundary.

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 explicit when-to-use guidance and no named alternative among the six siblings. The only routing rule given is internal ('ambiguous work is routed for human conformance review'), which describes downstream behavior rather than when an agent should pick this tool over classification-rates or conformance-draft.

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