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

Get DOL Foreign Labor Disclosure Files

foreign_labor_files

Retrieve official DOL OFLC disclosure workbook, record-layout, and auxiliary file URLs for LCA, PERM, H-2A, H-2B, or CW by specifying visa program, fiscal year, and quarter.

Instructions

Discover official DOL OFLC disclosure workbook, record-layout, and auxiliary file URLs for LCA, PERM, H-2A, H-2B, or CW.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fiscalYearNoDOL fiscal year, 2020 through 2030.
visaProgramNoForeign labor program: LCA, PERM, H-2A, H-2B, or CW.
fiscalQuarterNoFiscal quarter: Q1, Q2, Q3, or Q4.
Behavior3/5

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

With no annotations, the description must disclose traits. It states 'Discover' but does not mention read-only nature, authentication, or side effects. It is minimally adequate but adds no behavioral context beyond the obvious.

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?

One sentence, efficient, front-loaded with the verb. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple file URL discovery tool with 3 params and no output schema, the description is fairly complete. It could mention file formats, but overall it adequately informs the agent.

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% with clear parameter descriptions. The tool description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 verb 'Discover' and the resource 'file URLs', specifying the programs (LCA, PERM, H-2A, H-2B, CW). It distinguishes from sibling tools like foreign_labor_search and foreign_labor_fields.

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?

No explicit guidance on when to use this tool versus alternatives like foreign_labor_search or lca_disclosure_files. The description implies its purpose but does not provide when-not or alternative recommendations.

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