Skip to main content
Glama

Aturan.org — Indonesian Legal Retrieval

baca_isi_pasal_batch

Baca teks lengkap beberapa Pasal ketika regulation_id dan nomornya sudah diketahui.

Gunakan untuk 1–20 Pasal, boleh lintas regulasi. Untuk satu Pasal gunakan baca_isi_pasal.

Tool ini terutama digunakan setelah discovery melalui cari_peraturan_terkait: pilih regulasi yang relevan, ambil regulation_id dan nomor Pasal kandidat dari semantic_hit_pasals, lalu baca beberapa norma yang diperlukan dalam satu batch.

Tool ini juga dapat digunakan setelah cari_judul_peraturan apabila regulasi sudah diketahui dan beberapa nomor Pasal perlu dibaca sekaligus.

Hasil cari_pasal_terkait tidak perlu dibaca ulang melalui tool ini secara default karena tool tersebut sudah melakukan retrieval pada tingkat Pasal. Jangan mengumpulkan hasil cari_pasal_terkait lalu membacanya kembali secara batch kecuali terdapat alasan khusus untuk melakukan direct read berdasarkan regulation_id dan nomor Pasal yang sudah diketahui.

Jangan mengarang regulation_id atau nomor Pasal. Jika alamat norma belum diketahui dan tujuan riset adalah menemukan regulasi yang relevan untuk kemudian dibaca normanya, gunakan cari_peraturan_terkait terlebih dahulu.

Jika beberapa Pasal sudah diketahui dan diperlukan pada tahap analisis yang sama, prioritaskan satu pemanggilan batch hingga 20 item daripada memanggil baca_isi_pasal berulang atau membaginya menjadi beberapa batch kecil tanpa kebutuhan.

Kirim hanya Pasal yang relevan; jangan menambah item atau menunda pembacaan hanya untuk memenuhi kapasitas 20. Jika lebih dari 20 Pasal diperlukan, bagi menjadi beberapa batch, masing-masing maksimal 20 item.

Hasil mengikuti urutan input: identitas item, ok, serta data atau error. Periksa ok setiap item. Gunakan hanya hasil yang berhasil dibaca sebagai sumber bunyi norma; jangan menganggap seluruh batch berhasil hanya karena pemanggilan selesai.

Jika kredit tidak cukup, item tersebut dan item berikutnya yang belum diterima tidak melakukan retrieval. Item in-flight tetap selesai; tidak ada retry otomatis setelah refund.

Satu pemanggilan batch memakai satu slot scheduler akun; kredit tetap per item.

Contoh: {"items": [{"regulation_id": "004967", "pasal": "1"}]}. Jangan sertakan title, url, atau metadata lain pada item.

Args: items: Array 1–20 objek dengan regulation_id string ID enam digit dan pasal string nomor Pasal, misalnya 1, 5A, atau 1336.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses per-item ok checking, partial-failure semantics under insufficient credits, no automatic retry after refund, and that one batch consumes one scheduler slot with credits charged per item. It also restates return ordering, which the output schema likely already covers, so this is not fully additive.

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?

Purpose and scope are front-loaded, and the sentence-by-sentence content is mostly load-bearing guidance. However the batch-size rule is stated twice and the discovery-workflow admonitions run long, so there is mild redundancy rather than tight economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batch-read tool with an output schema, the description supplies everything the output schema cannot: when to prefer it over baca_isi_pasal, the credit/scheduler cost model, partial-failure handling, and item fabrication warnings. An agent has all it needs to call it correctly.

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 single nested 'items' parameter is given real semantic depth beyond the schema: 1–20 range, cross-regulation allowance, concrete examples ('1', '5A', '1336'), and an explicit exclusion ('Jangan sertakan title, url, atau metadata lain pada item'). It overlaps somewhat with the schema's own field descriptions, so not a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb (baca) and resource (teks lengkap beberapa Pasal) plus the precondition (regulation_id dan nomornya sudah diketahui). It explicitly distinguishes itself from its closest sibling: 'Untuk satu Pasal gunakan baca_isi_pasal.' An agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It names the upstream discovery tools (cari_peraturan_terkait, cari_judul_peraturan), states an explicit when-not (do not re-read cari_pasal_terkait results by default), and gives the ordering priority (prefer one batch up to 20 over repeated single reads). This is a complete routing guide.

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.

Resources