Skip to main content
Glama

Ezkielyna Public Tools

Prakiraan cuaca / Weather forecast

prakiraan_cuaca
Read-onlyIdempotent

Prakiraan cuaca BMKG per kelurahan/desa (per 3 jam, hingga 3 hari): kondisi, suhu, kelembapan, angin, tutupan awan. Needs the Kemendagri village code "adm4" (format 00.00.00.0000, e.g. 31.71.03.1001 = Kemayoran, Jakarta Pusat). BMKG weather forecast for an Indonesian village, 3-hourly for up to 3 days. Free, no key.

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": {
      "adm4": "<adm4>"
    },
    "name": "prakiraan_cuaca"
  }
}

Input Schema

NameRequiredDescriptionDefault
adm4YesKemendagri level-4 (kelurahan/desa) code, e.g. 31.71.03.1001.
daysNoHow many calendar days to return (1-3), counted from the first forecast date (today, local time). Default 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful context beyond that: the data source (BMKG), the 3-hourly cadence capped at 3 days, the village-level scope, and that no API key is required. It does not discuss failure modes for invalid or non-existent 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?

The scope and field list are front-loaded in the first sentence, and the prerequisite follows immediately. The main inefficiency is a bilingual restatement: the final English sentence largely repeats the opening Indonesian sentence's content, which adds length without new 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?

For a simple two-parameter, read-only lookup with no output schema, the description covers everything an agent needs: what is returned (condition, temperature, humidity, wind, cloud cover), the time resolution and horizon, and the exact identifier format required. Nothing essential is missing.

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 description coverage is 100%, so both adm4 and days are already fully documented, including the regex pattern, the example code, and the 1-3 range with default. The description restates the adm4 format and adds the provenance (Kemendagri village code) but says nothing about the days parameter. Baseline 3 is appropriate when the schema carries the load.

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?

The description names a specific verb+resource (BMKG weather forecast per kelurahan/desa) and enumerates the returned fields (kondisi, suhu, kelembapan, angin, tutupan awan) plus granularity (3-hourly, up to 3 days). It is unambiguous about what the tool does, but it never positions itself relative to sibling tools such as cari_wilayah or validasi_kode, which plausibly help obtain the required adm4 code.

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?

It states a concrete prerequisite ("Needs the Kemendagri village code adm4") with the exact format and a worked example, plus an access note ("Free, no key"), which gives an agent clear context for invoking it. It stops short of any when-not-to-use guidance or explicit routing to the code-lookup siblings.

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