Skip to main content
Glama

Find an employment attorney

find_employment_attorney
Read-only

Provide a state, a known city or both lat and lng. 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.

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_employment_attorney"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in degrees. Supply together with lng.
lngNoLongitude in degrees. Supply together with lat.
cityNoOptional city to tighten the search center (e.g. "Tampa").
limitNoMax attorneys to return (1–25).
stateNoUS state, e.g. "FL" or "Florida". Provide a state, a known city or a coordinate pair.
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.

Output Schema

NameRequiredDescriptionDefault
totalNoListings returned.
locationNoThe location searched and how it was resolved.
attorneysNoPublic-source attorney listings, nearest first.
_attributionNoSource and disclaimer for this result: Workers' Rights, its URL, the attribution line, and that the result is educational information, not legal advice.
directory_pausedNoTrue when the attorney directory is paused.
unsupported_filtersNoRequested filters the listings do not support.
directory_disclaimerNoWhat the listings are and are not.
representation_noticeNoNotice about attorney-client relationships.
excluded_defense_heavyNoListings left out because court records show mostly employer-side work.
listings_available_without_those_filtersNoListings that exist without the unsupported filters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / description
      Added value: +"Provide a state, a known city or both lat and lng."
    • addedInput schema / minProperties
      Added value: +1
    • changedInput schema / properties / lat / description
      Previous value: -"Optional precise latitude. Overrides city/state when paired with lng."New value: +"Latitude in degrees. Supply together with lng."
    • addedInput schema / properties / lat / maximum
      Added value: +90
    • addedInput schema / properties / lat / minimum
      Added value: +-90
    • changedInput schema / properties / lng / description
      Previous value: -"Optional precise longitude. Overrides city/state when paired with lat."New value: +"Longitude in degrees. Supply together with lat."
    • addedInput schema / properties / lng / maximum
      Added value: +180
    • addedInput schema / properties / lng / minimum
      Added value: +-180
    • changedInput schema / properties / state / description
      Previous value: -"US state — 2-letter code or full name (e.g. \"FL\" or \"Florida\"). Required unless lat/lng given."New value: +"US state, e.g. \"FL\" or \"Florida\". Provide a state, a known city or a coordinate pair."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "_attribution": {
      +      "description": "Source and disclaimer for this result: Workers' Rights, its URL, the attribution line, and that the result is educational information, not legal advice.",
      +      "properties": {
      +        "disclaimer": {
      +          "type": "string"
      +        },
      +        "line": {
      +          "type": "string"
      +        },
      +        "source": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "attorneys": {
      +      "description": "Public-source attorney listings, nearest first.",
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "directory_disclaimer": {
      +      "description": "What the listings are and are not.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "directory_paused": {
      +      "description": "True when the attorney directory is paused.",
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "excluded_defense_heavy": {
      +      "description": "Listings left out because court records show mostly employer-side work.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "listings_available_without_those_filters": {
      +      "description": "Listings that exist without the unsupported filters.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "location": {
      +      "description": "The location searched and how it was resolved.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "representation_notice": {
      +      "description": "Notice about attorney-client relationships.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "description": "Listings returned.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "unsupported_filters": {
      +      "description": "Requested filters the listings do not support.",
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. 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."
  5. 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."
  6. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / required
      Removed value: -[
      -  "min_rating",
      -  "radius_miles",
      -  "limit"
      -]
  7. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare readOnly/openWorld/non-destructive, but the description goes well beyond them: it discloses data provenance ('public-source', 'source-attributed'), that person-specific filters only apply where the directory supports them, that Google Places metrics are firm/office-level and never individual ratings, and that listings are neither state-bar verification nor an endorsement. These are exactly the caveats an agent needs before presenting results to a user.

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?

Four tight sentences with no filler, and the disclaimer is correctly placed last. Minor weakness: it leads with an input requirement rather than the purpose statement, so the 'what this does' sentence arrives second and the opening reads as a schema restatement.

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

Completeness5/5

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

For an open-world lookup with 10 mostly optional parameters and an output schema, the description covers the preconditions (US location), the result shape (proximity-sorted, source-attributed), the filter-support caveat, and the non-endorsement disclaimer. Nothing material is left for the agent to guess.

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%, so the baseline is 3; the description earns a bump by explaining the cross-cutting semantics of the person-specific filters (min_rating, language, fee filters) — that they apply only where the underlying directory publishes such data, and that office-level ratings must not be read as attorney ratings. This answers the main interpretive risk (a zero-result filter response) without re-listing every parameter.

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?

States a specific verb and resource: 'Find public-source employment-law attorney listings near a US location', plus the return content (identity, firm, location, contact, proximity-sorted). That is clearly a discovery/search tool, distinguishable from siblings like get_attorney_track_record or find_similar_cases. It does not explicitly name any sibling, so it stops short of a 5.

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 through the geographic requirement ('Provide a state, a known city or both lat and lng', 'near a US location'), but that requirement is already stated in the schema's state/description fields, so it adds little. There is no guidance on when to prefer this over get_attorney_track_record or explain_my_rights, and no exclusions beyond 'US location'.

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.

Resources