Skip to main content
Glama

Fuzzzy Law: Georgian law

search_law

Read-onlyIdempotent

Search Georgian law articles by words. Search in Georgian, with the terms the law itself uses; if the results are off the point, search again with the law's own word and ignore also_searched terms that do not fit. Returns matching articles with an exact text snippet, code, article number, official matsne.gov.ge link and version date. found=false means nothing matched: say so, never guess. კანონის მუხლების ძიება სიტყვებით: ზუსტი ამონარიდი, კოდექსი, მუხლის ნომერი, ოფიციალური ბმული და თარიღი.

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": "search_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoOptional: limit to one code (id or name).
limitNoHow many articles.
queryYesWhat to look for, best in Georgian legal terms, e.g. 'სააპელაციო საჩივრის ვადა'.

Output Schema

NameRequiredDescriptionDefault
foundYes
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.
messageNo
resultsYes
also_searchedNoThe law's own terms the search added for everyday words in the query.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add the failure contract (found=false means nothing matched; say so, never guess) and the notion of also_searched terms, but the return shape it lists is largely redundant with the output schema.

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 front-loaded English sentences: scope and query strategy first, then the return contract and the failure case. The Georgian sentence restates the same content for localization, which is reasonable but adds no new information for an agent reading both.

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?

With annotations and an output schema present, the description only needs to carry strategy and failure handling, and it does both. The only remaining gaps are the semantics of limit/paging behavior and when to constrain by code, which is a minor shortfall for a three-parameter tool.

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 description coverage is 100%, so each parameter is already documented, which sets the baseline at 3. The description adds real meaning for query phrasing (Georgian legal terminology, retry strategy) but says nothing about the code or limit parameters beyond what the schema already states.

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?

The description gives a specific verb and resource: 'Search Georgian law articles by words', and the word-level retrieval scope implicitly separates it from full-text retrieval siblings such as get_article or browse_code. It stops short of naming or explicitly contrasting any sibling, so it is clear but not fully differentiated.

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?

It gives concrete guidance: search in Georgian with the terms the law itself uses, and if the results miss, retry with the law's own wording and ignore also_searched terms that do not fit. It never states when to prefer a sibling like search or find_court_practice, so this is clear context without explicit exclusions.

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.