Skip to main content
Glama

Fuzzzy Law: Georgian law

browse_code

Read-onlyIdempotent

Show a code's structure: its chapters, or the article numbers and titles of one chapter. კოდექსის სტრუქტურა: თავები ან ერთი თავის მუხლების ნომრები და სათაურები.

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

Input Schema

NameRequiredDescriptionDefault
codeYesCode id from list_codes (e.g. civil_code, labour_code) or its Georgian name (e.g. შრომის კოდექსი).
limitNoArticles per page.
offsetNoSkip this many articles.
chapterNoOptional chapter to list articles of.

Output Schema

NameRequiredDescriptionDefault
codeYes
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.
offsetNo
messageNo
articlesNo
chaptersNo
code_nameNo
source_urlYesOfficial matsne.gov.ge link for this text.
version_dateNoDate of the consolidated version this text comes from.
version_noteNoPresent when a version date is unknown or text may be incomplete.
in_force_sinceNoDate this article's current wording took effect, if known.
total_articlesNo
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

B3.4/5.0
Behavior3/5

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

Annotations already declare a safe, read-only, idempotent operation, so the safety burden is covered. The description adds the structural-shape behavior (chapters vs. chapter contents) but says nothing about pagination behavior, even though limit and offset exist, and an output schema is present to describe returns.

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 sentence is front-loaded and efficient, but the Georgian translation repeats the same content without adding information, making the definition roughly twice as long as needed for an English-reading agent.

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 fully documented four-parameter schema, an output schema, and annotations covering safety, the description is nearly complete for this tool's complexity. The main omission is any mention of paginated results when browsing a chapter.

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 all four parameters are already documented. The description does add meaning about the chapter parameter's effect on what is returned, but it does not explain pagination semantics beyond what the schema already says.

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: show a code's structure, either its chapters or the article numbers and titles of one chapter. That is enough for an agent to distinguish structural browsing from fetching a single article or listing codes, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the description: call without a chapter to see chapters, with a chapter to list its articles. There is no explicit when-to-use versus alternatives such as get_article or search_law, and no stated 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.