Skip to main content
Glama

BRAINIAC Prevailing Wage

Read classification rates

prevailing-wage_classification-rates

Return sourced base/fringe rates, notes, zones, and excerpts for a wage determination. Price $0.01 USDC. POST /api/v1/prevailing-wage/classification-rates. 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>"
    },
    "name": "prevailing-wage_classification-rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
wdIdYes
craftNo

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 disclose key operational traits: a per-call price of $0.01 USDC, the endpoint, and that unpaid calls fail with 402 without executing. It omits anything about idempotency or rate limits, but for a read endpoint the cost/payment-gating disclosure is the material behavior.

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?

Three short sentences, front-loaded with the return payload, then the commercial and failure terms. The raw API path and price are dense but arguably useful to an agent; nothing is padded.

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?

No output schema and no annotations mean the description must cover both behavior and parameters. It handles behavior well but leaves the "craft" parameter and the identifier format unexplained, so an agent knows what it gets back but not fully how to constrain the request.

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%, so the description must explain the two parameters and does not. "wdId" is only obliquely implied by "a wage determination," and the optional "craft" filter is never mentioned at all, leaving an agent to guess whether it narrows results by trade.

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?

Uses a specific verb and resource ("Return sourced base/fringe rates ... for a wage determination") and even enumerates the payload contents (rates, notes, zones, excerpts). It does not explicitly contrast itself with siblings like classification-validate or resolve, but the read-rates framing is unambiguous.

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?

Usage is only implied: an agent can infer this is the lookup step that precedes validation or payroll work, but there is no explicit when-to-use, when-not-to-use, or named alternative. The payment note (unpaid calls return 402) is a precondition rather than usage guidance.

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