Skip to main content
Glama

Anlık hava durumu (MGM)

hava_get_current

Retrieves current observed weather for a Turkish province or district from the Turkish State Meteorological Service, including temperature, feels-like, humidity, wind, pressure, precipitation, and conditions.

Instructions

Current observed weather (hava durumu, sıcaklık) for a Turkish province/district from the Turkish State Meteorological Service (MGM): temperature, feels-like, humidity, wind, pressure, precipitation, condition.

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": {
      "il": "<il>"
    },
    "name": "hava_get_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
ilYesİl adı veya plaka, ör. "İstanbul", "izmir", "6"
ilceNoİlçe, ör. "Kadıköy" (Türkçe karakter şart değil). Boşsa il merkezi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the upstream source (MGM) and that values are observed rather than modeled, but says nothing about data freshness/latency, behavior for unknown provinces or districts, or error conditions.

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?

A single tight sentence that front-loads the core scope (current observed weather, Turkish province/district) and then enumerates returned fields. The field list earns its place given there is no output schema, though the parenthetical "hava durumu, sıcaklık" is mildly redundant with the English text.

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, enumerating the returned measurements is the right compensation and makes the definition usable. Remaining gaps are minor: no note on freshness, coverage limits, or what happens when a district name is ambiguous or unmatched.

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 the baseline is 3. The description only restates that a province/district is required and adds no format or edge-case detail beyond what the schema already documents, including the "boşsa il merkezi" fallback.

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 resource and temporal scope ("Current observed weather") plus the authoritative source (MGM), which implicitly separates it from the forecast sibling. It does not name hava_get_forecast or hava_get_air_quality explicitly, so sibling differentiation is inferred rather than stated.

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 only implied: "current observed" signals now-conditions versus a forecast, but no explicit when-to-use, when-not-to-use, or alternative is named. An agent must reason about the distinction rather than being routed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.