Skip to main content
Glama

Endorsement Index: HUD multifamily loans

DOL Davis-Bacon wage decisions by county

wage_determination
Read-onlyIdempotent

List the U.S. Department of Labor's current Residential and Building general wage decisions for a county, with modification number, publish date and SAM.gov link. With state alone, lists the state's decisions and the counties each covers. Decisions are listed, never selected for a project: HUD labor standards staff make that selection.

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>"
    },
    "name": "wage_determination"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoLimit to one schedule. Omit for both.
limitNo
stateYesTwo-letter state code, e.g. TX.
countyNoCounty name, e.g. Harris. "County" or "Parish" is optional.
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the returned fields, the dual listing mode, and the important 'never selected for a project' responsibility boundary that no annotation conveys. It is silent on result capping/pagination, which is the main behavioral omission.

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?

Three sentences, front-loaded with the verb and resource, then the alternate mode, then the responsibility caveat. Every sentence carries information an agent needs and 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?

With no output schema, the description does well to name the returned fields, and the selection caveat is a valuable addition. The gap is pagination: limit defaults to 10 with a maximum of 50 and offset exists, but the description never signals that results are capped or that an agent may need to page for a whole state, which is a realistic failure mode here.

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 60%: state, county and type are documented in the schema, while limit and offset have no descriptions anywhere. The description does add real meaning about the effect of omitting county (state-level listing plus county coverage), which the schema does not state. However it never mentions limit/offset semantics, so it only partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ('List') with a specific resource ('DOL current Residential and Building general wage decisions') and names the returned fields (modification number, publish date, SAM.gov link). It also states the alternate listing mode ('With state alone, lists the state's decisions and the counties each covers'). No sibling tool in the set operates in this DOL/Davis-Bacon space, so confusion risk is effectively zero.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage boundary: decisions are 'listed, never selected for a project' and selection is the job of HUD labor standards staff, which tells an agent not to expect a recommendation. It also explains the state-only invocation case. It does not spell out when to narrow by county versus type, but that is reasonably inferable from the schema.

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