Skip to main content
Glama

Fuzzzy Law: Georgian law

list_changes

Read-onlyIdempotent

List the articles of a law that were amended, added or removed since a date, by consolidated version on matsne.gov.ge, with a link to each version. Use it to see whether a rule was different when the events happened. კანონის ცვლილებები მითითებული თარიღიდან: რომელი მუხლი შეიცვალა, დაემატა ან ამოიღეს და რომელ რედაქციაში.

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

Input Schema

NameRequiredDescriptionDefault
codeYesCode id from list_codes (e.g. civil_code, labour_code) or its Georgian name (e.g. შრომის კოდექსი).
sinceYesA date as YYYY-MM-DD, e.g. 2025-03-01.
articleNoOptional: only this article, e.g. 47.

Output Schema

NameRequiredDescriptionDefault
codeYes
foundYes
sinceNo
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.
changesNo
messageNo
code_nameNo
history_fromNoDate of the oldest stored version; nothing earlier is known.
total_changesNo
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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are organized by consolidated version and carry a link to each version, which is useful behavioral context, but says nothing about volume, pagination, or how far back coverage extends.

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 sentences: what it returns first, then when to use it. The Georgian sentence is a full restatement that carries no additional information for an agent reading the English text, which slightly inflates length without adding meaning.

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 a 100%-documented schema, a present output schema, and rich annotations, the description supplies everything an agent needs to decide to call it. Only the temporal coverage limit and result size are unaddressed, which are minor for this complexity.

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 code, since and article are all documented in the schema itself. The description reinforces the 'since a date' semantics but never mentions the optional article filter or the consolidated-version grouping as a parameter-level behavior, so it adds little 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?

States a specific verb and resource: list the articles of a law that were amended, added or removed since a date, grouped by consolidated version, with links. The scope (change history since a date) is distinct enough that an agent can separate it from get_article or browse_code, though no sibling is named explicitly.

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?

Gives a concrete use case: 'Use it to see whether a rule was different when the events happened.' That is clear context for picking this tool over fetching current law text, but there are no explicit exclusions or named alternatives, so it stops 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.