Skip to main content
Glama

Ezkielyna Public Tools

Detail kode wilayah / Code details

detail_kode
Read-onlyIdempotent

Menjelaskan satu kode wilayah: nama, jenis, semua induknya dan jumlah wilayah di bawahnya. Returns the name, kind, all parents (province down) and child count of a Kemendagri region code. Accepts 31.71.03.1001 or 3171031001. Level-4 codes are also the BMKG "adm4" codes. 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": {
      "kode": "<kode>"
    },
    "name": "detail_kode"
  }
}

Input Schema

NameRequiredDescriptionDefault
kodeYesRegion code, e.g. "32.73", "31.71.03" or "3171031001".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real context beyond them: it operates offline at no cost, returns the full ancestor chain, and its level-4 output doubles as BMKG adm4 codes.

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 meaning and then the return shape, with format examples in the middle. The Indonesian and English sentences duplicate each other's content, which is mild redundancy rather than waste, and every other sentence carries information.

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?

With no output schema, the description takes on the burden of describing returns and does so fully: name, kind, all parents down from province, and child count. For a single-parameter lookup tool this leaves nothing an agent needs in order to invoke it 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?

Schema coverage is 100% and the schema example already shows both dotted and undotted forms, so the description's '31.71.03.1001 or 3171031001' largely restates it. It does add one piece of meaning beyond the schema — that level-4 codes are BMKG adm4 codes — but stays at the baseline otherwise.

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?

A specific verb-plus-resource statement ('Menjelaskan satu kode wilayah') followed by an enumerated return shape (name, kind, parents, child count). The singular 'one code' implicitly separates it from search-style siblings like cari_wilayah or daftar_anak, though no sibling is named outright.

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

Usage Guidelines3/5

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

There is contextual guidance — the tool works offline and free, and level-4 codes correspond to BMKG adm4 codes, which tells the agent when the output is useful. However, there is no explicit when-to-use/when-not guidance and no routing against validasi_kode or cari_wilayah for overlapping code-lookup questions.

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