Skip to main content
Glama

GetLawED — Verified South African Law

Free consultation times

check_availability
Read-onlyIdempotent

Free consultation times at a firm on one date (South African time). Use a start time from here in request_consultation.

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

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD, within the next 60 days
firm_idYes
consultation_idYesFrom get_firm

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 safety is covered structurally. The description adds genuinely new information not in the schema: timestamps are interpreted in South African time, which prevents off-by-timezone booking errors. It stops short of describing the return shape (e.g., whether times are formatted, sorted, or filtered by availability).

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?

Two short sentences, zero filler, with the core purpose front-loaded and the downstream usage instruction second. Nothing is redundant with the title.

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 three-parameter read with rich annotations and no output schema, this is nearly complete: it conveys what is returned (available start times) in a specific timezone and how to consume it. Only the undescribed firm_id and the exact return format leave small gaps.

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 67%: date is documented as YYYY-MM-DD within 60 days and consultation_id as coming from get_firm. firm_id has no schema description and the tool description does not explain it either, and 'start time from here' describes the output rather than any input 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 resource and scope: free consultation times at a firm for a single date, with the timezone qualifier '(South African time)'. It is clearly distinct from the booking sibling request_consultation, though it doesn't explicitly name that contrast.

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?

Explicitly routes the agent downstream: 'Use a start time from here in request_consultation' tells the caller what to do with the result and implies this check precedes booking. No exclusions or failure-condition guidance are given.

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.