Skip to main content
Glama

Fuzzzy Law: Georgian law

verify_citation

Read-onlyIdempotent

Check a citation: does the article (and paragraph) exist, is it repealed, and what does it actually say. Pass quote to check a quotation word for word; the quote is looked for in the whole article, not only the paragraph named. Includes a word-and-number overlap check, not a legal judgement. ციტატის შემოწმება: არსებობს თუ არა მუხლი, რას ამბობს სინამდვილეში და ზუსტია თუ არა მოყვანილი ციტატა.

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": {
      "code": "<code>",
      "article": "<article>",
      "claim": "<claim>"
    },
    "name": "verify_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCode id from list_codes (e.g. civil_code, labour_code) or its Georgian name (e.g. შრომის კოდექსი).
claimYesWhat your answer says this article provides.
quoteNoOptional: words you quote from the article, to check they are in it word for word. Join left-out parts with …
articleYesArticle number as printed, e.g. 369, 48 or 166¹ (166-1 also works). A paragraph goes in its own argument. Check that article_number in the reply is the one you asked for.
paragraphNoOptional paragraph number, e.g. 1.

Output Schema

NameRequiredDescriptionDefault
codeYes
textNoWhat the article (or requested paragraph) actually says.
claimYes
existsYes
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.
articleYes
messageYes
source_urlNo
is_repealedNo
quote_checkNo
version_dateNo
version_noteNo
article_titleNo
lexical_checkNo
article_numberNo
in_force_sinceNo
paragraph_existsNo
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.
paragraph_requestedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower; the description still adds real value by disclosing the quote-matching scope (whole article, not just the paragraph) and by bounding the check as word-and-number overlap rather than legal interpretation.

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?

Purpose is front-loaded in the first sentence and the caveats follow compactly, but the Georgian sentence duplicates the English content and adds no new information for an agent, which is wasted length.

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 an output schema present and rich annotations, return values need not be explained; the description covers what is checked and its limits. Minor gap: it does not describe what a failed or mismatched verification looks like versus an error.

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 earns a point by explaining the interaction between the quote and paragraph parameters — the quote is searched across the entire article, overriding the narrower paragraph scope.

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 resource plus the three things it verifies: existence of the article/paragraph, repeal status, and actual content. This clearly separates it from retrieval siblings like get_article, though it never names an alternative explicitly.

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?

The quote guidance ('pass quote to check a quotation word for word') and the scope limit ('not a legal judgement') give implied usage context, but there is no explicit when-to-use versus get_article/search_law guidance and no stated exclusions or prerequisites.

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.