Skip to main content
Glama

Fuzzzy Law: Georgian law

search

Read-onlyIdempotent

Search Georgian law articles and court decisions. Returns ids, titles and official links; call fetch with an id for the full text. კანონებისა და გადაწყვეტილებების ძიება.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, best in Georgian legal terms, e.g. 'სააპელაციო საჩივრის ვადა'.

Output Schema

NameRequiredDescriptionDefault
resultsYes
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

A4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: it discloses the returned fields (ids, titles, official links) and the explicit two-step pattern of searching then fetching full text by id, which is exactly the kind of workflow information annotations cannot convey.

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?

Three short sentences, front-loaded with purpose, followed by the return contract and the next-step instruction. The trailing Georgian sentence is largely a duplicate of the opening sentence, which is mild redundancy rather than harmful padding.

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 one-parameter search tool with an output schema, this covers purpose, result shape and the downstream fetch step. The remaining gap is positioning relative to the several overlapping search siblings, which matters given the crowded sibling set.

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% and the single `query` parameter carries its own description with a concrete Georgian-language example. The description reinforces the domain expectation ('Georgian law articles and court decisions'), which confirms what belongs in the query, though it adds no syntax or formatting rules beyond the schema.

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 states a specific verb and resource set ('Search Georgian law articles and court decisions') and adds the return shape plus the follow-up path to `fetch`. It is clear what the tool does, but it does not distinguish itself from siblings like `search_law` or `find_court_practice`, which appear to overlap in scope.

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?

There is one explicit workflow rule: 'call fetch with an id for the full text', which tells the agent this is a discovery step rather than a retrieval step. However, there is no guidance on when to prefer this tool over the sibling search tools covering law versus court practice, so the choice among alternatives is left to inference.

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.