Skip to main content
Glama

Fuzzzy Law: Georgian law

find_court_practice

Read-onlyIdempotent

Find real decisions of Georgian courts on an issue: case number, court, date, exact snippet and link when stored. get_coverage lists the courts held; pass court to search one of them only. Read a decision with get_court_decision before you describe it. With status none_found, say in one line that no published decision was found in the collections held, up to decisions_through, and that this does not mean none exists. სასამართლო პრაქტიკა: რეალური გადაწყვეტილებები, საქმის ნომერი, თარიღი.

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": {
      "query": "<query>"
    },
    "name": "find_court_practice"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNoOptional: search only the Supreme Court (supreme) or only the Constitutional Court (constitutional).
limitNoHow many decisions.
queryYesWhat to look for, best in Georgian legal terms, e.g. 'სააპელაციო საჩივრის ვადა'.

Output Schema

NameRequiredDescriptionDefault
queryYes
noticeNoეს არის კანონის ტექსტი და წყარო, არა იურიდიული კონსულტაცია. ოფიციალური ტექსტი: matsne.gov.ge. This is law text and its source, not legal advice. The official text is on matsne.gov.ge; for important decisions consult a lawyer.
statusYes
messageYes
resultsYes
decisions_throughNoDate of the newest stored decision of the courts searched; later decisions are not covered.
freshness_warningNoSet when that check is overdue or its date is unknown; pass the warning on with the answer.
data_current_as_ofNoDate (ISO) the stored law texts were last confirmed against matsne.gov.ge. Tell the person this date.
decisions_through_by_courtNoThe same date for each court searched, by court name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds behavior beyond them: results include links only "when stored," coverage is bounded by decisions_through, and an empty result does not mean no decision exists. That last point is exactly the kind of caveat an agent cannot infer from structured fields.

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?

The core guidance is front-loaded in tight sentences with no filler, and each sentence carries an actionable rule. The closing Georgian line largely restates the English opening, adding length without new operational information.

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 a three-parameter lookup with full schema coverage and an output schema, the description covers what an agent still needs: how results are scoped, which sibling to call first and after, and how to report a zero-result outcome honestly. Nothing required to call or interpret it correctly is missing.

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 baseline is 3; the description still adds meaning for court by tying it to get_coverage's inventory and warning it searches only one court at a time. Query semantics ("on an issue") are reinforced, but limit is left entirely to the schema and the none_found/decisions_through terms appear without field-level mapping.

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?

The description opens with a specific verb and resource: "Find real decisions of Georgian courts on an issue," then enumerates the returned fields (case number, court, date, exact snippet, link). It explicitly distinguishes itself from get_coverage (court inventory) and get_court_decision (full read), so an agent can choose without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states concrete routing rules: call get_coverage to see which courts are held, pass court to restrict to one of them, and read a decision with get_court_decision before describing it. It also prescribes agent behavior for the none_found status, which is explicit when-to-use/when-not guidance rather than implied context.

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.