Skip to main content
Glama

Ezkielyna Public Tools

Validasi kode wilayah / Validate code

validasi_kode
Read-onlyIdempotent

Memeriksa format kode wilayah Kemendagri dan apakah kode itu ada di data Kepmendagri terbaru. Checks the format of a region code and whether it exists in the current list; for unknown codes it reports the nearest existing parent. 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": "validasi_kode"
  }
}

Input Schema

NameRequiredDescriptionDefault
kodeYesCode to check, e.g. "35.78.01.1001" or "3578011001".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the bar is lower. The description still adds real context beyond them: it runs offline and free, checks against the latest Kepmendagri data, and returns the nearest existing parent for unknown 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?

Two short, front-loaded sentences with no filler, and the key fallback behavior is included. The bilingual repetition is slightly redundant but matches the tool's audience and costs little.

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 single-parameter read-only validator with no output schema, the description covers what is checked, the data source, the fallback for unknown codes, and the offline nature. Only the precise result shape (valid vs. exists flags) is left implicit, which is a minor gap.

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 the schema already documents it fully with dotted and undotted example formats. The description adds only the notion of a 'kode wilayah Kemendagri', which is marginal over the schema's own wording; baseline 3 applies.

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 specific verb and resource: it checks the format of a Kemendagri region code and whether it exists in the current Kepmendagri list. The added note about reporting the nearest existing parent distinguishes it from a plain lookup, though no sibling (e.g. detail_kode, cari_wilayah) is named.

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?

Usage is implied by the word 'validate' and by the parent-fallback behavior, which suggests it is the tool to reach for when a code's existence is uncertain. There is no explicit when-not guidance or routing to alternatives such as looking up details or searching regions.

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