Skip to main content
Glama

BRAINIAC Prevailing Wage

Search Davis-Bacon wage determinations

prevailing-wage_search

Search Davis-Bacon wage determinations by state, county, construction type, or award/bid date. Results include source details and an indicator when a record may be out of date. Price $0.01 USDC. POST /api/v1/prevailing-wage/search. Unpaid calls return 402 and do not run.

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": "prevailing-wage_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
stateNo
countyNo
awardBidDateNo
constructionTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does add real value: it discloses the $0.01 USDC cost, the POST endpoint, that unpaid calls return 402 without executing, and that results carry source details plus an out-of-date indicator. However, it says nothing about authentication/payment mechanism, rate limits, pagination behavior, or whether results are sorted, which is a significant gap for a paid read endpoint with zero annotation coverage.

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, then result content, then cost/transport and the 402 failure mode. Nothing is padded, though the endpoint path is arguably redundant with the tool name for an agent that cannot issue raw HTTP.

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?

There is no output schema and no annotations, so the description should fully specify behavior; it covers return-content shape and failure mode well, but omits two of six parameters and any guidance on combining filters or whether all filters are ANDed.

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% across 6 parameters; the description names four (state, county, constructionType, awardBidDate) but leaves query and limit undocumented, and never states the allowed constructionType values (building/residential/highway/heavy), the 2-character state code constraint, or the 50/100 limit default and cap.

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 resource ("Search Davis-Bacon wage determinations") and enumerates the searchable facets: state, county, construction type, award/bid date. This distinguishes it from the sibling payroll/conformance tools, but it never explicitly contrasts itself with prevailing-wage_classification-rates, which could also return wage data.

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 filter list implies when the tool is useful (lookup of determinations by geography/type/date), but there is no explicit when-to-use vs. when-not-to-use guidance and no mention of the sibling tools. Usage must be inferred from the parameter surface.

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