Skip to main content
Glama
UHQ-Actual
by UHQ-Actual

Search DOL LCA Disclosure Data

lca_search

Search official DOL OFLC LCA disclosure data by employer, worksite, job title, SOC code, NAICS code, case status, visa class, wage, and date range.

Instructions

Search official DOL OFLC LCA disclosure XLSX data by employer, worksite, job title, SOC, NAICS, status, visa class, wage, and dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoWorksite or employer city substring filter.
stateNoTwo-letter worksite or employer state filter.
dateToNoInclusive upper date bound in YYYY-MM-DD form.
quarterNoFiscal quarter, 1 through 4.
socCodeNoSOC code prefix filter.
dateFromNoInclusive lower date bound in YYYY-MM-DD form.
jobTitleNoJob title substring filter.
dateFieldNoDOL date field to filter on, default DECISION_DATE.
localFileNoOptional path to an already-downloaded official LCA disclosure XLSX file.
naicsCodeNoNAICS code prefix filter.
visaClassNoVisa class, such as H-1B, H-1B1, or E-3.
caseStatusNoCase status, such as CERTIFIED or DENIED.
fiscalYearNoFederal fiscal year, such as 2026.
maxResultsNoMaximum rows to return.
searchModeNoEmployer match mode.
employerNameNoEmployer name filter.
minAnnualWageNoMinimum annualized offered wage.
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention any side effects, data freshness, rate limits, pagination behavior, or whether the data is live or cached. The description only states the search action, which is insufficient for a tool with 17 parameters.

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?

The description is a single sentence of 18 words, efficiently listing the key filter dimensions without repetition or fluff. It is front-loaded with the main action and resource.

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?

The description does not mention output format, pagination, or interpretation of results. With no output schema and 17 parameters, the description should at least hint at the nature of results (e.g., list of LCAs) or how maxResults affects output. It is incomplete for an agent to use effectively.

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 100%, so each parameter already has a brief description. The tool description adds no new meaning beyond grouping filter types (employer, worksite, etc.). With full schema coverage, baseline score of 3 applies.

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 clearly states the resource (official DOL OFLC LCA disclosure XLSX data) and the action (search by various filters). It enumerates multiple filter dimensions, making the tool's purpose specific and distinct from sibling tools like foreign_labor_search or lca_employer_profile.

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 description implies usage by listing search filters, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., foreign_labor_search for broader LCA data). No when-not-to-use or prerequisite information is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/UHQ-Actual/DOL_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server