Skip to main content
Glama

Idn Mk Review Detail

idn_mk_review_detail
Read-onlyIdempotent

Metadata and PDF for one Indonesian Constitutional Court judicial-review resume or DPR analysis document from the DPR RI register, given the url returned by idn_mk_review_search: full title, document kind, MK case number, statute under review, publication year and the resume PDF from berkas.dpr.go.id. Use after idn_mk_review_search to read the ruling summary.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://jdih.dpr.go.id/setjen/view/info-judicial-review-putusan-mahkamah-konstitusi-nomor-21-puu-xxi-2023-perihal-pengujian-undang-undang-nomor-29-tahun-2004-tentang-praktik-kedokteran-terhadap-undang-undang-dasar-negara-republik-indonesia-tahun-1945"
    },
    "name": "idn_mk_review_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA jdih.dpr.go.id/setjen/view/... url from idn_mk_review_search (the slug after /setjen/view/ also works).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds real value beyond that by enumerating what the response contains (full title, document kind, MK case number, statute, publication year, resume PDF) and naming the source host berkas.dpr.go.id, though it omits any note on rate limits or missing-document behavior.

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?

Front-loaded with the retrieval action and the returned fields, then closes with the sequencing instruction. The first sentence is dense with an enumerated field list but every element earns its place; no filler.

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?

There is no output schema, yet the description compensates by listing exactly which metadata fields and the PDF are returned, and it pins the required input to the search tool's url. An agent has everything needed to call and interpret this tool correctly.

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?

Only one parameter and schema description coverage is 100%, so the schema fully documents url, including that the slug after /setjen/view/ also works. The description reinforces the source ('given the url returned by idn_mk_review_search') but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource: retrieves metadata and PDF for one Indonesian Constitutional Court judicial-review resume/DPR analysis document. It explicitly contrasts with the sibling idn_mk_review_search ('given the url returned by...'), so an agent can distinguish this detail-fetch from the search tool without opening either 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?

Gives an explicit when-to-use and the sequencing dependency: 'Use after idn_mk_review_search to read the ruling summary,' and names the sibling as the source of the required url. Nothing about invocation order is left to inference.

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.