Skip to main content
Glama

Get processing times and the pending queue

get_queue
Read-onlyIdempotent

DOL's processing times (average days, and the month each queue is working on when DOL prints one), the filing month DOL is deciding by PERM Tracker's daily check of case statuses (perm.decidingNow: DOL stopped printing a PERM month on Oct 31 2026), the oldest month still open, and the pending PERM cases by filing month. Example: {}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
asOfYesThe date the data is true for, YYYY-MM-DD, when one applies.
dataYesThe answer, or found: false when no record matched.
pageYesThe page on permtracker.app that shows the same thing. Cite it.
sourceYesWho published the underlying records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered. The description adds real context beyond that: provenance and freshness ('PERM Tracker's daily check of case statuses') and a data caveat that DOL stopped printing a PERM month on Oct 31 2026, which changes how perm.decidingNow should be interpreted. It does not discuss caching or latency, but with an output schema present the return shape needn't be described.

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

Conciseness3/5

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

It is a single sentence with no filler, but it is a heavily nested run-on with stacked parentheticals ('the filing month DOL is deciding by PERM Tracker's daily check of case statuses (perm.decidingNow: ...)'), which makes the key facts hard to scan. It would read better as a short front-loaded statement followed by a bulleted field list.

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?

With an output schema present, the description's job is mostly to frame the data, and it does that: what each aggregate means, where the numbers come from, and one important caveat about DOL's printed month. The remaining gap is selection guidance against the sibling estimation and visa-bulletin tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. The trailing 'Example: {}' correctly signals a no-argument call, and the baseline for a 0-param tool applies.

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 enumerates the concrete payload: DOL processing times (average days, printed queue month), the month DOL is deciding by PERM Tracker's daily status check, the oldest open month, and pending PERM cases by filing month. That is specific and lets an agent recognize this as the backlog/queue-status read. It stops short of a crisp verb+resource opening and never distinguishes itself from siblings such as estimate_decision or get_visa_bulletin.

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 statement, no prerequisite, and no named alternative. An agent must infer from the field list that this is the right call for 'where is the PERM queue / how long are DOL processing times' questions, and gets no signal about when estimate_decision would be the better choice.

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.