Skip to main content
Glama

BRAINIAC Prevailing Wage

Resolve a wage determination

prevailing-wage_resolve

Resolve an active determination by state, county, construction type, and award/bid date. Unmatched determinations are not inferred. Price $0.01 USDC. POST /api/v1/prevailing-wage/resolve. 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": {
      "state": "<state>",
      "county": "<county>",
      "constructionType": "<constructionType>",
      "awardBidDate": "<awardBidDate>"
    },
    "name": "prevailing-wage_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
countyYes
awardBidDateYes
constructionTypeYes

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 supplied, the description carries real behavioral weight: it discloses the price ($0.01 USDC), the transport (POST /api/v1/prevailing-wage/resolve), and that unpaid calls return 402 and do not execute. It also warns that unmatched determinations are not inferred, which sets expectations about failure results, though it does not state whether this is a read-only operation or what a successful response contains.

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, front-loaded with the purpose and the scoping inputs before the cost and failure-mode details. The endpoint path is mildly redundant with structured metadata, but every sentence otherwise carries operational value.

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?

For a paid lookup with no annotations and no output schema, the definition covers inputs, cost, payment failure, and the unmatched case. It falls short on two things an agent needs: the concrete success response shape, and whether an unmatched determination yields an error, an empty result, or a null - 'not inferred' is ambiguous.

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 0%, so the description must compensate, and it partially does by naming all four required inputs and clarifying that awardBidDate may be an award or a bid date. However, it never explains that state must be a two-character code, what format the county takes, or which construction-type values are accepted, all of which the schema leaves undocumented.

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 gives a specific verb (resolve) and a specific resource (an active wage determination), scoped by the four lookup dimensions. An agent can tell this is a determination lookup rather than a rates or payroll tool, though it never explicitly contrasts itself with the sibling search tool.

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 when-to-use guidance and no mention of alternatives such as a search or validation tool that might precede a resolve. The only conditional statement ('unmatched determinations are not inferred') is a behavioral constraint on the result, not guidance on when to call this tool.

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