Skip to main content
Glama

GetLawED — Verified South African Law

Law firm details and consultations

get_firm
Read-onlyIdempotent

Details of one firm: about, location, practice areas, languages, and the consultations it offers (with duration, price and any deposit).

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>"
    },
    "name": "get_firm"
  }
}

Input Schema

NameRequiredDescriptionDefault
firm_idYesFirm id from find_law_firms

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description contributes beyond that by disclosing the response contents, notably that consultation entries carry duration, price, and possible deposit, which matters because no output schema exists. It does not address error behavior for a bad firm_id.

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?

A single sentence with zero filler; the key noun ('one firm') and the returned-content list are front-loaded and every clause carries information.

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 simple single-entity read with rich annotations and one fully documented parameter, the definition is nearly complete, and it compensates for the absent output schema by naming the returned fields. The only omission is behavior on an invalid or missing firm_id.

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?

There is one parameter at 100% schema description coverage, so the schema already documents firm_id and even its provenance ('Firm id from find_law_firms'). The description adds no format, example, or validation detail beyond that, so the baseline of 3 applies.

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 singular resource ('Details of one firm') and enumerates the content returned: about, location, practice areas, languages, and consultations with duration, price, and deposit. The singular framing implicitly contrasts with the plural listing sibling find_law_firms, but it never names or explicitly contrasts with it.

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?

No sentence says when to use this tool versus alternatives such as find_law_firms or check_availability. Usage is only implied by the singular 'one firm' framing and by the schema note that firm_id comes from find_law_firms, which suggests a lookup-after-search workflow without stating it.

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.