Skip to main content
Glama

Workers' Rights

by com.workers-rights
OverviewDiscussionsAdmin

Find an employment attorney

find_employment_attorney
Read-only

Find public-source employment-law attorney listings near a US location. Returns source-attributed identity, firm, location, and contact data sorted by proximity. Person-specific filters and fields apply only where the underlying directory supports them; Google Places metrics are labeled as firm/office listing data, never individual ratings. Listings are not state-bar verification or an endorsement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoOptional precise latitude. Overrides city/state when paired with lng.
lngNoOptional precise longitude. Overrides city/state when paired with lat.
cityNoOptional city to tighten the search center (e.g. "Tampa").
limitNoMax attorneys to return (1–25).
stateNoUS state — 2-letter code or full name (e.g. "FL" or "Florida"). Required unless lat/lng given.
languageNoFilter on attorney-supplied language data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than silently implying no attorneys are nearby.
min_ratingNoMinimum individual-profile rating. Office/business ratings are never treated as an attorney rating, so this matches only hand-managed profiles and returns nothing where none exist.
radius_milesNoSearch radius. Defaults to 100mi for broad statewide coverage.
contingency_feeNoFilter on attorney-supplied fee data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than implying no attorneys are nearby.
free_consultationNoFilter on attorney-supplied fee data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than implying no attorneys are nearby.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed4 schema fields changed
    • changedInput schema / properties / contingency_fee / description
      Previous value: -"Filter source-supported attorney fee data; Google office listings are excluded."New value: +"Filter on attorney-supplied fee data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than implying no attorneys are nearby."
    • changedInput schema / properties / free_consultation / description
      Previous value: -"Filter source-supported attorney fee data; Google office listings are excluded."New value: +"Filter on attorney-supplied fee data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than implying no attorneys are nearby."
    • changedInput schema / properties / language / description
      Previous value: -"Filter source-supported attorney language data; Google office listings are excluded."New value: +"Filter on attorney-supplied language data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than silently implying no attorneys are nearby."
    • changedInput schema / properties / min_rating / description
      Previous value: -"Minimum individual-profile rating; Google office ratings are excluded."New value: +"Minimum individual-profile rating. Office/business ratings are never treated as an attorney rating, so this matches only hand-managed profiles and returns nothing where none exist."
  3. Changed4 schema fields changed
    • changedInput schema / properties / contingency_fee / description
      Previous value: -"Only attorneys who work on contingency (no upfront fee)."New value: +"Filter source-supported attorney fee data; Google office listings are excluded."
    • changedInput schema / properties / free_consultation / description
      Previous value: -"Only attorneys offering a free initial consultation."New value: +"Filter source-supported attorney fee data; Google office listings are excluded."
    • changedInput schema / properties / language / description
      Previous value: -"Filter to attorneys who speak this language, e.g. \"Spanish\"."New value: +"Filter source-supported attorney language data; Google office listings are excluded."
    • changedInput schema / properties / min_rating / description
      Previous value: -"Minimum star rating (0–5)."New value: +"Minimum individual-profile rating; Google office ratings are excluded."
  4. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / required
      Removed value: -[
-  "min_rating",
-  "radius_miles",
-  "limit"
-]
  5. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses data provenance (public-source), result attribution, sorting, and important limitations: person-specific filters only apply when the directory supports them, and Google Places metrics are never presented as individual attorney ratings. This is substantive behavioral context that protects against misuse.

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: the first states the exact purpose and scope, the second summarizes return data and ordering, the third states caveats. Every sentence carries distinct, non-redundant information, and the core purpose is front-loaded.

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?

The description provides enough about return content and limitations for a tool with no output schema, and the schema richly documents all parameters, including required-state semantics. Minor gap: it doesn't restate the state-or-lat/lng requirement, but that is fully covered by schema descriptions, so it doesn't materially hurt completeness.

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 description coverage is 100%, so the baseline is 3. The description adds cross-cutting meaning that isn't in any single parameter: person-specific filters apply only where the underlying directory supports them, and Google Places metrics are labeled as firm/office data, never individual ratings. This helps the agent reason about filter behavior globally.

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 states a specific verb ('Find'), a specific resource ('public-source employment-law attorney listings'), and scope ('near a US location'). It also lists return fields (source-attributed identity, firm, location, contact data) and sorting, clearly distinguishing this from general legal-research or track-record siblings.

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?

Usage context is implied by the description (finding attorneys near a location), and the caveat that listings are not state-bar verification or an endorsement hints at non-uses. However, it does not explicitly say when to prefer this tool instead of siblings like get_attorney_track_record or explain_my_rights.

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

All Workers' Rights toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources