Skip to main content
Glama

Find cases without a case number

find_cases
Read-onlyIdempotent

Find a case from what you know about it: any of the employer's name, words of the job title and the law firm, with one filing day, a range of days or no date. One of them is enough. Each case comes with its number, status, job and filing day, and the answer says what DOL's record holds for the days read. With no employer fitting in a month or less, it returns the employers that did file in those days under a close spelling. Example: {"employer":"Acme","from":"2026-01-05","to":"2026-01-31"}.

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": "find_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoThe last filing day of a range. A range longer than three months needs an employer or a firm. Example: 2026-01-31.
jobNoWords of the job title, up to 80 characters. Alone, with no dates, it reads the newest three months. Example: controls engineer.
firmNoThe law firm's or agent's name, 2 to 120 characters. DOL names a firm only once it decides a case, so the answer holds decided cases only. Example: Fragomen.
fromNoThe first filing day of a range. Alone, it is that one day. Example: 2026-01-05.
filedNoOne filing day, from 2019-10-01 to today. Not with from or to. Example: 2026-01-30.
programNoWhich program to search. Example: perm.
employerNoThe employer's name, 2 to 120 characters. Inc, LLC and punctuation don't matter. With dates three months apart or less, any word of the name fits; with no dates or a longer range, the start of the name. Example: Acme.

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

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world safety, but the description adds real behavioral context beyond them: what each returned case carries, that the answer reports what DOL's record holds for the days read, that firm filters yield decided cases only, and that a fuzzy-spelling employer list is returned when nothing fits. It stops short of pagination, result limits, or performance characteristics.

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 core capability and the 'any one of them is enough' rule are front-loaded, and a concrete invocation example closes the description. The prose is dense in places (date-mode rules, firm caveat, fuzzy fallback all in a few clauses), but no sentence is wasted.

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 seven-parameter, zero-required search tool with an output schema, the description covers inputs, combination rules, return contents and an edge-case fallback. Return values are summarized even though the output schema exists, and only pagination/result-count behavior is left unaddressed.

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?

Schema coverage is 100% and includes enums and length bounds, so the baseline is 3; the description earns more by explaining cross-parameter combination semantics ('One of them is enough') and the date-mode interplay that individual schema properties only partially state. It does not add format or syntax detail beyond the schema's examples.

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 states a specific verb and resource ('Find a case') and the title plus first clause ('from what you know about it') distinguish it from a by-number lookup such as get_case. It never names a sibling explicitly, so the differentiation is implied rather than spelled out.

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 clearly explains what may be combined ('any of the employer's name, words of the job title and the law firm, with one filing day, a range of days or no date. One of them is enough') and the schema reinforces date-range constraints. There is no explicit statement of when to prefer this over get_case or the search_* tools, so routing guidance is incomplete.

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.