Skip to main content
Glama

Fuzzzy Law: Georgian law

get_coverage

Read-onlyIdempotent

What this service holds: the laws with their version dates and how far back their earlier wordings go, the court decisions and their date range, and what is not held. Call it when unsure whether a topic is covered. რა ინახება სერვისში: კანონები და მათი რედაქციების თარიღები, სასამართლო გადაწყვეტილებები და ის, რაც არ ინახება.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
lawsYes
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.
not_coveredYesWhat this connector does not hold. Say so instead of answering from memory when a question needs one of these.
court_decisionsYes
how_data_is_keptNoWhere each kind of data comes from, how it is collected and how it is kept current. Use it when the person asks where the information comes from or how up to date it is.
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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it reports historical version depth and court-decision date ranges, and notably reports negative coverage ("what is not held"), which is the key trait an agent needs before deciding whether to search.

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 two tight, front-loaded sentences with no waste. However, the entire description is then repeated verbatim in Georgian, roughly doubling length without adding information for an agent that already parsed the first version.

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 zero parameters, rich annotations, and an output schema handling return structure, the description needs only to say what is covered and when to ask. It does both. The only missing piece is guidance on what to do after coverage is confirmed, e.g. which search sibling to call next.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline applies. The description correctly avoids inventing parameter behavior for a no-arg call.

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?

"What this service holds" plus an enumeration of the three things returned (law texts with version dates and historical depth, court decisions with date range, and explicitly what is absent) makes the resource concrete and distinct from siblings like search_law or get_article. The verb is implicit rather than stated, which keeps it just short of a 5.

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?

"Call it when unsure whether a topic is covered" gives a clear triggering condition that an agent can act on without inference. It stops short of naming when not to call it or pointing to a specific alternative sibling once coverage is confirmed.

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.