Skip to main content
Glama

Ezkielyna Public Tools

Cari wilayah / Search regions

cari_wilayah
Read-onlyIdempotent

Mencari provinsi, kabupaten/kota, kecamatan atau desa/kelurahan berdasarkan nama (tahan salah ketik). Searches Indonesian administrative regions by name (typo tolerant) and returns the Kemendagri code plus the full path, e.g. "Desa X, Kec. Y, Kab. Z, Prov. W". Extra words can name a parent ("gambir jakarta pusat"). Offline, free.

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": {
      "nama": "<nama>"
    },
    "name": "cari_wilayah"
  }
}

Input Schema

NameRequiredDescriptionDefault
namaYesNama wilayah / region name, e.g. "Kemayoran", "kab bandung", "desa sukamaju garut". Max 200 chars.
batasNoMax results (default 10, max 50).
jenisNoOptional exact kind (finer than tingkat).
tingkatNoOptional level: 1 provinsi, 2 kabupaten/kota, 3 kecamatan, 4 desa/kelurahan.
kode_indukNoOptional parent code to search inside, e.g. "32" (Jawa Barat) or "32.05" (Kab. Garut).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the bar is lower. Beyond that, the description adds real context the annotations don't: typo tolerance, offline/free (no auth or rate concerns), and the response shape (code + full path with a worked example). It does not say what happens on zero matches or how ties are ordered.

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 core action, then return format, then the multi-word trick, then the offline note, with no filler. The Indonesian/English duplication costs some length but is justified for a bilingual service and each version stays tight.

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 no output schema, the description correctly compensates by describing the returned code and full path plus an example. Combined with full schema coverage and safety annotations, an agent has what it needs to call it; only no-result and ambiguity behavior are unstated.

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 baseline is 3, and the description goes beyond it by explaining that free-form extra words in `nama` act as a parent qualifier, which clarifies how to combine `nama` with the parent-scoping direction of `kode_induk`. Details for `batas`, `jenis`, and `tingkat` remain in the schema, which is fine.

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?

Names a specific verb and resource ("Searches Indonesian administrative regions by name") and enumerates the covered region types (provinsi through desa/kelurahan), which no sibling tool touches. It also states what is returned (Kemendagri code plus full path), so an agent can distinguish it immediately from validasi_kode/detail_kode.

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 clear context for use: name-based lookup, typo tolerant, and that extra words can name a parent ("gambir jakarta pusat"), which is genuinely actionable query guidance. It stops short of exclusions or routing to siblings such as detail_kode for code-based lookups, but the surrounding tools operate in unrelated domains.

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