Skip to main content
Glama

Ezkielyna Public Tools

Daftar wilayah di bawah kode / List children

daftar_anak
Read-onlyIdempotent

Mendaftar wilayah satu tingkat di bawah kode (provinsi → kab/kota → kecamatan → desa/kelurahan), dengan halaman. Lists the direct children of a code, paginated with offset/batas. Without kode it lists the 38 provinces. Offline, free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "daftar_anak"
  }
}

Input Schema

NameRequiredDescriptionDefault
kodeNoParent code, e.g. "32" or "32.73.01". Leave empty for all provinces.
batasNoPage size (default 50, max 200).
offsetNoStart position (use next_offset from the previous page).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered structurally. The description adds genuinely useful traits beyond that: offline operation, free of charge, and the no-argument default of 38 provinces. It does not describe the shape of a returned child record, which matters because there is no output schema.

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?

Two tight sentences, front-loaded with the action and hierarchy, followed by pagination, the default case, and the offline/free note. The bilingual Indonesian/English pairing duplicates content, which costs a little density but aids matching for either language.

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

Completeness3/5

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

For a 3-parameter read-only tool with full schema coverage and annotations, the essentials are present. However, with no output schema the description never says what a child entry contains (code, name, level) or what next_offset looks like, leaving the agent to discover the return shape at call time.

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% and the schema already explains kode, batas (default 50, max 200) and offset (including the next_offset tip). The description nevertheless adds real semantic value by clarifying that kode denotes a parent whose immediate children are returned and that an empty kode defaults to the province level.

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?

States a concrete verb and resource: "Lists the direct children of a code," and pins down the hierarchy (provinsi → kab/kota → kecamatan → desa/kelurahan) plus the no-code case (38 provinces). It is unambiguous on its own, but it never contrasts itself with siblings like cari_wilayah (name search) or detail_kode, so the agent must infer the boundary.

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?

Gives usable context: call with a code to walk the hierarchy one level at a time, call without kode to get the 38 provinces, and paginate with offset/batas. It stops short of explicit when-not guidance or naming an alternative tool for name-based lookup, so it is clear rather than complete.

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