Skip to main content
Glama

GetLawED — Verified South African Law

Request a consultation (the firm confirms)

request_consultation

Request a consultation at a firm for the person you are helping. This is a REQUEST: the firm first checks for conflicts of interest and then confirms or declines by email. Only use details the person gave you, and only with their consent. Do not include confidential or privileged details — a one-line reason is enough.

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": {
      "firm_id": "<firm_id>",
      "consultation_id": "<consultation_id>",
      "start": "<start>",
      "client_name": "<client_name>",
      "client_email": "<client_email>",
      "client_phone": "<client_phone>",
      "reason": "<reason>",
      "consent": "<consent>"
    },
    "name": "request_consultation"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesA start time returned by check_availability (ISO 8601)
reasonYesOne or two sentences on what the consultation is about (no confidential details)
consentYestrue only if the person agreed that their details may be shared with this firm to arrange the consultation
firm_idYes
client_nameYesFull name of the person
client_emailYes
client_phoneYesMobile number, e.g. 082 123 4567
other_partiesNoNames of any other people or companies involved — lets the firm check for conflicts of interest
assistant_nameNoName of the AI assistant making the request (optional)
consultation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare the mutation profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), but the description adds the crucial post-call behavior: the firm reviews for conflicts and responds by email with confirmation or decline. It also imposes a data-minimization constraint (no confidential/privileged details, one-line reason) that is nowhere in the annotations. This is exactly the extra context the annotations cannot carry.

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 short sentences, front-loaded with the purpose and the async nature of the request. The confidentiality and consent constraints follow in priority order with no filler or repetition.

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 mutation tool with 8 required parameters and no output schema, the description covers the important unknowns: that success means 'submitted, pending review' and that the answer arrives by email. It does not explain what the immediate response contains or what to do if the firm declines, which would be helpful given there is no output schema.

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

Parameters3/5

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

Schema coverage is 70%, so the baseline is 3. The description adds genuine meaning for 'reason' (one line, no confidential details) and reinforces consent, but says nothing about firm_id, consultation_id, start, or other_parties—all of which an agent must populate across 8 required parameters.

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?

Opens with a specific verb and resource: 'Request a consultation at a firm for the person you are helping.' The word 'REQUEST' in caps plus the follow-on sentence makes clear this submits a pending request rather than a confirmed booking, which separates it from check_availability in the sibling list. It stops short of naming the sibling it depends on for the 'start' value, so the differentiation is implied rather than stated.

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 the operative condition for calling: only use details the person provided and only with their consent. The consequence of calling is spelled out (firm checks conflicts, then confirms or declines by email), which tells an agent this is an async hand-off, not an instant booking. No explicit exclusion or 'use X instead' routing, so it falls short of a 5.

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.