Skip to main content
Glama

BRAINIAC Prevailing Wage

Draft a classification conformance request

prevailing-wage_conformance-draft

Prepare optional SF-1444 request language from caller-supplied facts. Human review and contracting-officer submission are required; this is not an approved classification or rate. Price $0.01 USDC. POST /api/v1/prevailing-wage/conformance-draft. 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": {
      "projectName": "<projectName>",
      "wdId": "<wdId>",
      "duties": "<duties>"
    },
    "name": "prevailing-wage_conformance-draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
wdIdYes
dutiesYes
rationaleNo
projectNameYes
proposedRateNo
proposedClassificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 it discloses unusually concrete behavior: a $0.01 USDC cost, the POST endpoint, and the fact that unpaid calls return 402 and do not execute. It also flags that output is unapproved draft language requiring human review — a meaningful safety disclosure. It stops short of describing the returned document or persistence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each doing distinct work: purpose, disclaimer, price, and payment failure mode. Purpose and scope are front-loaded, and nothing is redundant.

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?

Cost, payment behavior, and the non-authoritative nature of the output are well covered for a paid generative tool with no annotations or output schema. The gap is input guidance: with 0% schema coverage, an agent gets no help choosing or formatting the six fields, which is the main thing still missing.

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 six parameters (projectName, wdId, duties, rationale, proposedRate, proposedClassification), so the description must compensate and largely does not. 'From caller-supplied facts' is the only gesture toward inputs; it never explains what duties or wdId should contain, nor how proposedRate/proposedClassification interact with the draft.

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 and artifact: 'Prepare optional SF-1444 request language from caller-supplied facts,' which tells an agent exactly what is produced. It also preempts confusion by stating 'this is not an approved classification or rate,' distinguishing it from the validate/rates siblings, though it does not name those siblings directly.

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 word 'optional' plus the SF-1444 framing implies this is a discretionary drafting step rather than a verification step, and 'Human review and contracting-officer submission are required' signals the downstream workflow. However, it never says when to choose this over siblings like prevailing-wage_classification-validate or classification-rates, leaving the comparison to inference.

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