Skip to main content
Glama

BRAINIAC Prevailing Wage

Reconcile fringe credits

prevailing-wage_fringe-reconcile

Compare annualized benefit contributions and cash-in-lieu with the supplied required hourly fringe. Inputs and findings are returned for review. Price $0.02 USDC. POST /api/v1/prevailing-wage/fringe-reconcile. 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": {
      "planCostAnnual": "<planCostAnnual>",
      "annualHours": "<annualHours>",
      "projectHours": "<projectHours>",
      "reportedPlanContribution": "<reportedPlanContribution>",
      "reportedCashInLieu": "<reportedCashInLieu>",
      "requiredFringeHourly": "<requiredFringeHourly>"
    },
    "name": "prevailing-wage_fringe-reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
annualHoursYes
projectHoursYes
planCostAnnualYes
reportedCashInLieuYes
requiredFringeHourlyYes
reportedPlanContributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose genuinely useful facts beyond the schema: the endpoint, the $0.02 USDC price, and that unpaid calls fail with 402 without executing. It also says inputs and findings are returned for review, implying a non-persistent computation. However, it never states whether the tool mutates state, how findings are framed (pass/fail, per-hour shortfall), or what happens on invalid input, leaving the core behavioral contract unclear.

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?

The description is four short sentences, front-loaded with the purpose before payment and transport details. Nothing is redundant. Slightly better structure would group the payment/endpoint notes separately from the functional statement, but the size is appropriate.

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 six-parameter computation with no annotations and no output schema, the description leaves too much unexplained, particularly the annualization logic that determines whether a fringe credit is adequate. It does at least signal that inputs are echoed back with findings, which compensates a little for the missing output schema. The parameter-level silence makes it inadequate overall.

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 required parameters, so the description must compensate and it largely does not. It gestures at three of them (annualized benefit contributions, cash-in-lieu, required hourly fringe) but says nothing about units, how annualHours and projectHours interact with planCostAnnual to derive an hourly credit, or what reportedPlanContribution versus planCostAnnual means. An agent would have to guess at the annualization arithmetic.

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 opening sentence gives a specific verb and resource: it compares annualized benefit contributions plus cash-in-lieu against a supplied required hourly fringe. That is far more informative than the title alone and clearly separates it from payroll-report or classification-validate siblings. It stops short of naming an alternative or stating a precise scope boundary, so it does not reach a 5.

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 or when-not-to-use guidance and no mention of prerequisites such as having already run payroll-precheck or classification-rates. The only conditional content is about payment (402 on unpaid calls), which is invocation mechanics, not usage guidance. An agent must infer the workflow position entirely from the tool name.

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