Skip to main content
Glama

Son depremler

deprem_get_recent

Retrieve recent earthquakes in and around Türkiye from AFAD or Kandilli, ordered by occurrence time descending, with filters for hours, minimum magnitude, and province.

Instructions

Recent earthquakes in and around Türkiye (son depremler, deprem listesi) from AFAD or Kandilli Observatory, newest first. Filter by hours, minimum magnitude and province (il).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deprem_get_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
ilNoİl filtresi, ör. "İzmir" (Türkçe karakter şart değil)
saatNoSon kaç saat (1–720, varsayılan 24)
limitNoEn fazla kaç kayıt döndürülsün (1–200, varsayılan 20)
kaynakNoVeri kaynağı: AFAD veya Kandilliafad
minBuyuklukNoEn küçük büyüklük, ör. 3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It adds useful traits beyond the schema — the two upstream providers and the newest-first ordering — but says nothing about what a returned record contains, what happens if a provider is unavailable, or whether results are cached or rate-limited.

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 sentences with the resource and scope front-loaded, then the filter set. No filler, though the parenthetical Turkish aliases are keyword padding that mostly duplicates the title 'Son depremler'.

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 five-parameter, zero-required read tool with no output schema and no annotations, the description covers the essentials an agent needs: what it returns topically, where the data comes from, and how it is ordered. The remaining gap is that with no output schema, the shape of an earthquake record is never described.

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%, and every parameter (il, saat, limit, kaynak, minBuyukluk) is fully documented with ranges, defaults, and an enum in the schema itself. The description's sentence 'Filter by hours, minimum magnitude and province (il)' merely restates three of those fields and omits the source and limit levers, so it adds no meaning beyond the structured data. Baseline 3 applies.

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?

The description pairs a specific verb and resource ('Recent earthquakes in and around Türkiye') with the concrete upstream sources (AFAD, Kandilli), the geographic scope, and the sort order ('newest first'). It also includes the Turkish query aliases (son depremler, deprem listesi), so an agent can match this tool to a user request without opening the schema.

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?

It states the available narrowing dimensions (hours, minimum magnitude, province) which implies when this tool is the right one, but never says when not to use it or points at any alternative for historical or non-Türkiye seismic data. Usage is inferable rather than stated.

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