Skip to main content
Glama

Fuzzzy Law: Georgian law

fetch

Read-onlyIdempotent

Fetch the full text, official link and version details behind a search result id. ძიების შედეგის სრული ტექსტი და ოფიციალური ბმული.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id from search, e.g. article:civil_code:138.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

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?

Read-only, idempotent, non-destructive behavior is already covered by annotations, while the description adds useful scope concerning content, provenance, and version information. It does not explain invalid or stale-id behavior or how version details are selected, so the additional behavioral transparency remains modest.

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?

The English sentence is front-loaded and compact, covering the operation, input expectation, and result scope. The Georgian sentence provides localization but partially repeats the English and omits version details, creating slight redundancy.

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?

For a one-parameter read operation with a fully described input and an output schema, this is nearly enough to select and invoke the tool correctly. The main remaining gaps are routing versus sibling getters and clarification of id validity and version behavior, rather than any need to restate the return schema.

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 coverage is 100%, and the `id` field already documents both its search origin and an example such as `article:civil_code:138`. The description reinforces that relationship but adds no further syntax, lifetime, or compatibility constraints, so the high-coverage baseline applies.

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?

The description gives a concrete operation and payload: resolving a search-result id to "the full text, official link and version details." That makes the generic name `fetch` understandable, but it does not explicitly distinguish this resolver from sibling retrieval tools such as `get_article` or `get_court_decision`.

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?

The phrase "behind a search result id" establishes the intended workflow: use it after search when the result's underlying document and metadata are needed. It does not state when a direct sibling getter should be preferred or whether ids from other tools are accepted.

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.