Pasal.id — Indonesian Law

Laporkan Masalah Data

report_issue

Laporkan masalah data Pasal.id dari alur MCP saat pengguna meminta pelaporan. Panggil jika teks Pasal yang diambil tampak rusak/terpotong/tidak konsisten karena OCR, atau jika pengguna menyatakan isinya salah, atau jika peraturan/Pasal yang seharusnya ada tidak ditemukan (OCR salah, peraturan hilang, Pasal hilang, tautan rusak, konten usang, kegagalan pencarian). Jangan spam pada zero-result eksplorasi pencarian biasa. Hanya report_type yang wajib; judul diturunkan otomatis jika kosong.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Tahun peraturan.
`title`	No	Judul pendek dalam Bahasa Indonesia. Opsional — jika kosong, judul diturunkan otomatis dari report_type dan kutipan peraturan/Pasal.
`law_id`	No	law_id Pasal.id jika sudah diketahui.
`node_id`	No	node_id dari section yang bermasalah pada hasil read_law untuk koreksi OCR; jangan menebak ID ayat yang tidak dikembalikan.
`law_type`	No	Jenis peraturan, misalnya UU atau PP.
`law_number`	No	Nomor peraturan.
`description`	No	Konteks tambahan. Jelaskan apa yang pengguna harapkan dan langkah yang sudah dicoba.
`report_type`	Yes	Jenis masalah yang dilaporkan. Salah satu nilai: ocr_correction, missing_regulation, missing_pasal, incorrect_content, broken_link, outdated_content, search_failure, other.
`pasal_number`	No	Nomor Pasal yang bermasalah jika relevan.
`contact_email`	No	Email kontak opsional jika pengguna ingin dapat dihubungi.
`reference_url`	No	URL sumber pendukung, misalnya PDF resmi.
`current_content`	No	content_text dari section yang sama dengan node_id pada hasil read_law. Wajib untuk ocr_correction.
`expected_citation`	No	Kutipan peraturan yang seharusnya muncul untuk report_type=search_failure, misalnya 'UU No. 27 Tahun 2022'.
`suggested_content`	No	Teks koreksi yang disarankan. Wajib untuk ocr_correction.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

changedInput schema / properties / current_content / description

Previous value: -"Teks saat ini dari get_pasal. Wajib untuk ocr_correction."New value: +"content_text dari section yang sama dengan node_id pada hasil read_law. Wajib untuk ocr_correction."

changedInput schema / properties / node_id / description

Previous value: -"node_id dari get_pasal untuk koreksi OCR."New value: +"node_id dari section yang bermasalah pada hasil read_law untuk koreksi OCR; jangan menebak ID ayat yang tidak dikembalikan."

Changed18 schema fields changedSep 30, 2026

addedInput schema / properties / contact_email / description

Added value: +"Email kontak opsional jika pengguna ingin dapat dihubungi."

addedInput schema / properties / current_content / description

Added value: +"Teks saat ini dari get_pasal. Wajib untuk ocr_correction."

addedInput schema / properties / description / description

Added value: +"Konteks tambahan. Jelaskan apa yang pengguna harapkan dan langkah yang sudah dicoba."

addedInput schema / properties / expected_citation

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Kutipan peraturan yang seharusnya muncul untuk report_type=search_failure, misalnya 'UU No. 27 Tahun 2022'."
+}

addedInput schema / properties / law_id / description

Added value: +"law_id Pasal.id jika sudah diketahui."

addedInput schema / properties / law_number / description
```
Added value: +"Nomor peraturan."
```

addedInput schema / properties / law_type / description

Added value: +"Jenis peraturan, misalnya UU atau PP."

addedInput schema / properties / node_id / description

Added value: +"node_id dari get_pasal untuk koreksi OCR."

addedInput schema / properties / pasal_number / description

Added value: +"Nomor Pasal yang bermasalah jika relevan."

addedInput schema / properties / reference_url / description

Added value: +"URL sumber pendukung, misalnya PDF resmi."

addedInput schema / properties / report_type / description

Added value: +"Jenis masalah yang dilaporkan. Salah satu nilai: ocr_correction, missing_regulation, missing_pasal, incorrect_content, broken_link, outdated_content, search_failure, other."

addedInput schema / properties / suggested_content / description

Added value: +"Teks koreksi yang disarankan. Wajib untuk ocr_correction."

addedInput schema / properties / title / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / title / default
```
Added value: +null
```

addedInput schema / properties / title / description

Added value: +"Judul pendek dalam Bahasa Indonesia. Opsional — jika kosong, judul diturunkan otomatis dari report_type dan kutipan peraturan/Pasal."

removedInput schema / properties / title / type
```
Removed value: -"string"
```
addedInput schema / properties / year / description
```
Added value: +"Tahun peraturan."
```

changedInput schema / required

Previous value: -[
-  "report_type",
-  "title"
-]New value: +[
+  "report_type"
+]

First observedApr 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare write (readOnlyHint=false), non-destructive, non-idempotent, open-world. The description adds useful behavior beyond that: only report_type is mandatory, the title is auto-derived when empty, and current_content/suggested_content become required for ocr_correction. It does not say where the report lands or whether there is deduplication, but the added conditional-context is meaningful.

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?

A single dense paragraph that front-loads the purpose, then conditions, then the anti-spam caveat, then the required-parameter note. Every sentence carries weight, though the enumeration of failure modes is slightly long.

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 14-parameter write tool with an output schema and full schema coverage, the description supplies the decision context an agent needs to decide whether to file a report. It omits only downstream details (where the report goes, expected response), which the output schema partially covers.

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 the schema already documents all 14 parameters, including the ocr_correction requirements for current_content and suggested_content. The description mostly restates what the schema says (report_type required, title auto-derived), adding little beyond the baseline.

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 description states a specific verb+resource: reporting data problems with Pasal.id content encountered during the MCP flow. It is clearly distinguishable from all siblings (read_law, search_legal, resolve_law), none of which are reporting tools.

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 gives explicit when-to-call conditions (corrupted/truncated OCR text, user says content is wrong, missing regulation/Pasal, broken link, outdated content, search failure) and an explicit when-not-to: don't spam reports on ordinary zero-result search exploration. Alternatives and exclusions are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pasal.id — Indonesian Law tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.