Skip to main content
Glama

Legal help options for a legal problem

get_help_first_answer
Read-onlyIdempotent

Use when the person asks for a lawyer or legal help but has not chosen a lawyer yet, including short requests like "I need a lawyer". From their short description of the legal need (plus state, city and legal problem if they named them), it returns: up to five listed lawyers when the matter and state are known (in the listing's own order), local legal aid and court self-help with sources and dates, fees a lawyer published, the official license-check site, and at most one follow-up question. Read-only: it stores nothing, sends nothing and contacts no one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "get_help_first_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity the person already named, if any.
stateNoTwo-letter U.S. state the person already named, if any.
messageYesShort description of the legal need in the person's words (for example "I need a lawyer for my eviction in Fresno"). Used only to read the type of problem, the place and any deadline or cost concern; not stored.
legal_problemNoA few words for the legal problem the person already named, if any (for example "eviction").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / message / description
      Previous value: -"The person's latest message, in their own words."New value: +"Short description of the legal need in the person's words (for example \"I need a lawyer for my eviction in Fresno\"). Used only to read the type of problem, the place and any deadline or cost concern; not stored."
    • changedInput schema / properties / message / maxLength
      Previous value: -2000New value: +1000
  2. Changed1 schema field changed
    • removedInput schema / properties / attorney_id
      Removed value: -{
      -  "description": "A listed lawyer the person asked about (for fees or license), if any.",
      -  "format": "uuid",
      -  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      -  "type": "string"
      -}
  3. Changed6 schema fields changed
    • removedInput schema / properties / approved_preview_id
      Removed value: -{
      -  "description": "Only the id of a preview the person explicitly approved in preview_client_message. Never set from general chat.",
      -  "maxLength": 80,
      -  "type": "string"
      -}
    • changedInput schema / properties / attorney_id / description
      Previous value: -"A listed lawyer the conversation is about (for fees or license), if known."New value: +"A listed lawyer the person asked about (for fees or license), if any."
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "City the person already named, if any.",
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / properties / history
      Removed value: -{
      -  "description": "Only the person's own earlier messages about this legal question, oldest first, so facts they already gave are not asked again. Leave out anything else.",
      -  "items": {
      -    "additionalProperties": false,
      -    "properties": {
      -      "role": {
      -        "enum": [
      -          "user"
      -        ],
      -        "type": "string"
      -      },
      -      "text": {
      -        "maxLength": 1000,
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "role",
      -      "text"
      -    ],
      -    "type": "object"
      -  },
      -  "maxItems": 10,
      -  "type": "array"
      -}
    • addedInput schema / properties / legal_problem
      Added value: +{
      +  "description": "A few words for the legal problem the person already named, if any (for example \"eviction\").",
      +  "maxLength": 120,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Two-letter U.S. state the person already named, if any.",
      +  "pattern": "^[A-Za-z]{2}$",
      +  "type": "string"
      +}
  4. Changed4 schema fields changed
    • changedInput schema / properties / history / description
      Previous value: -"Earlier turns of this conversation, oldest first, so facts the person already gave are not asked again."New value: +"Only the person's own earlier messages about this legal question, oldest first, so facts they already gave are not asked again. Leave out anything else."
    • changedInput schema / properties / history / items / properties / role / enum
      Previous value: -[
      -  "user",
      -  "assistant"
      -]New value: +[
      +  "user"
      +]
    • changedInput schema / properties / history / items / properties / text / maxLength
      Previous value: -2000New value: +1000
    • changedInput schema / properties / history / maxItems
      Previous value: -20New value: +10
  5. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds real value: it enumerates what the caller gets back (up to five lawyers in listing order, legal aid, court self-help with sources and dates, published fees, official license-check site, at most one follow-up question) and the condition governing that output (matter and state known). The closing 'stores nothing, sends nothing and contacts no one' usefully reassures against side effects such as contacting attorneys, though it partly restates the annotations.

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?

Two sentences, front-loaded with the usage trigger before the return inventory. The second sentence is long and list-heavy, but each clause carries information the agent cannot get from annotations or the schema; there is no filler or repetition of the title.

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?

There is no output schema, so the description correctly spends its words describing the return contents and the one-follow-up-question cap. Together with annotations covering safety and a fully documented 4-parameter schema, an agent has everything needed to decide when to call it and what to expect.

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, but the description adds meaning: it frames state, city, legal_problem and message as facts the person 'already named', reinforcing that the agent should pass conversational context rather than interrogate the user. It also explains a behavioral dependency the schema cannot express - the lawyer list only appears when matter and state are known.

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?

States a specific verb and resource: returns legal help options (listed lawyers, legal aid, court self-help, fees, license-check site) for a person who has asked for a lawyer but has not chosen one. The audience condition and the returned contents make it clearly separable from lookups like get_attorney_profile or find_attorneys without opening the schema.

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?

Gives an explicit trigger ('Use when the person asks for a lawyer or legal help') and explicitly covers short/underspecified requests like 'I need a lawyer'. It also implies the boundary condition ('has not chosen a lawyer yet'), which tells the agent this is the entry point rather than a follow-up lookup, though it does not name a specific sibling to use instead once a lawyer is chosen.

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