Skip to main content
Glama

Fuzzzy Law: Georgian law

get_article

Read-onlyIdempotent

Get the full exact text of one article, with its paragraphs, official link, version date and the previous and next article. Use it to check deadlines, amounts and ages before stating them. Pass as_of (a date) for the newest matsne version dated on or before that day; its changes may have taken effect later, so give the version date. ერთი მუხლის სრული ზუსტი ტექსტი, ოფიციალური ბმული და რედაქციის თარიღი; as_of თარიღით მიიღებ იმ დღემდე ბოლო რედაქციას.

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

Input Schema

NameRequiredDescriptionDefault
codeYesCode id from list_codes (e.g. civil_code, labour_code) or its Georgian name (e.g. შრომის კოდექსი).
as_ofNoOptional date as YYYY-MM-DD: return the newest matsne version dated on or before that day instead of the current one (its changes may have taken effect later).
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
foundYes
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.
articleNo
messageNo
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
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: as_of returns the newest version dated on or before the given day, and the caveat that a version's changes may take effect later than its date — a non-obvious temporal semantic the agent would otherwise get wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The English portion is tight and front-loaded, but the trailing Georgian sentence restates the same content (full text, official link, version date, as_of semantics) rather than adding anything. That is duplication that lengthens the definition without new information for the primary reader.

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?

An output schema exists, so return values need no explanation, and all four parameters are fully covered by the schema plus the as_of note. For a single-record lookup tool the definition is essentially complete, with only minor room to state prerequisites such as needing a code from list_codes.

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 every parameter is already documented in the schema; the description's as_of explanation largely restates it. It adds only a small nudge, telling the agent to report the version date when answering, which is marginal beyond the structured fields.

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?

States a specific verb and resource ('Get the full exact text of one article') plus the exact payload returned: paragraphs, official link, version date, previous and next article. That scope makes it distinguishable from search_law, browse_code and get_court_decision without opening any schema.

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?

'Use it to check deadlines, amounts and ages before stating them' gives a concrete usage context tied to verification, and the as_of sentence explains when to supply a date. It stops short of naming an alternative (e.g. use search_law to find an article first) or stating exclusions, so it is short of a 5.

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.