Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

turkey_earthquakes_afad_official_data

Read-onlyIdempotent

Turkey Earthquakes - AFAD Official Data: Real-time structured data extraction feed for Turkey Earthquakes - AFAD Official Data.

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": "turkey_earthquakes_afad_official_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the word "real-time," without clarifying data freshness/latency, update cadence, source reliability, or result ordering — the traits that actually matter for a live feed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the length comes from redundancy rather than economy: the tool name/title is repeated verbatim and the phrase "structured data extraction feed" is filler. There is no wasted length in the sense of bloat, but every sentence is essentially a restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one optional parameter) and has annotations, but it lacks an output schema, so the description should describe what a record contains (magnitude, location, depth, timestamp) and the geographic scope. None of that is provided, leaving an agent unable to predict the response.

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?

There is a single optional parameter (maxResults) with 100% schema description coverage, so the schema fully documents it. The description adds no meaning beyond the schema, which matches the baseline of 3 when structured fields do the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name and title twice ("Turkey Earthquakes - AFAD Official Data") and adds only the phrase "real-time structured data extraction feed." It conveys the resource domain but is essentially tautological, offering no verb-level specification of what the tool actually retrieves or returns.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives such as europe_mediterranean_earthquakes_emsc_official_data or earthquake_monitor_usgs_emsc_afad. No scope, exclusions, or selection criteria are stated; the agent must infer usage from the name alone.

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