Skip to main content
Glama

GitJog — Hungarian legislation

Egy § szövege egy időállapotban

szakasz
Read-onlyIdempotent

Egy jogszabály egy §-a (horgony vagy §-szám szerint), opcionálisan egy adott napon hatályos szöveggel. § nélkül a jogszabály metaadatát, időállapot-listáját és tartalomjegyzékét adja (nem a teljes szöveget).

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": {
      "slug": "<slug>"
    },
    "name": "szakasz"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesA jogszabály slugja, pl. „2013-evi-cxxii-torveny-foldforgalmi” (a `kereses` adja).
datumNoIdőállapot napja (YYYY-MM-DD): az ezen a napon hatályos szöveg. Alap: a legutolsó.
horgonyNoA § horgonya, pl. „6-272-sz-megbizasi-szerzodes” (a `kereses` vagy a tartalomjegyzék adja).
paragrafusNoA § száma horgony helyett: „18. §”, „6:272. §”, „18/A. §”.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / horgony / description
      Previous value: -"A § horgonya, pl. „18-sz-elovasarlasi-jog” (a `kereses` vagy a tartalomjegyzék adja)."New value: +"A § horgonya, pl. „6-272-sz-megbizasi-szerzodes” (a `kereses` vagy a tartalomjegyzék adja)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / horgony / maxLength
      Added value: +200
    • addedInput schema / properties / paragrafus / maxLength
      Added value: +200
    • addedInput schema / properties / slug / maxLength
      Added value: +200
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive lookup. The description adds valuable behavioral detail beyond that: without a section it returns metadata, time-state list and TOC rather than full text, and datum selects the text in force on that day with the latest as default.

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

Conciseness5/5

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

Two compact sentences with no wasted wording. The primary section-text use case is front-loaded, and the no-section fallback is stated immediately after.

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 four parameters, full schema coverage, and safety annotations present, the description covers the important behavioral modes and default date behavior. It does not detail output shape, but this is acceptable because there is no output schema and the description already states what each mode returns.

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?

Schema coverage is 100%, so the schema already explains each parameter. The description still adds meaning by clarifying the alternative use of horgony versus paragrafus and by explaining the mode switch when no section parameter is supplied.

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 states a specific verb and resource: it returns one section (§) of a legal statute, either by anchor or section number, optionally as of a given date. It also clearly describes the no-section mode, but it does not explicitly differentiate itself from sibling tools such as fetch or kereses.

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 through the two modes: include horgony or paragrafus to get a section text, omit them to get metadata, time-state list and table of contents. However, there is no explicit guidance on when to use this tool instead of siblings like kereses, fetch, diff, or valtozasok.

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.