Skip to main content
Glama
Sign In
GMPSignal Real-Time Intelligence MCP (59 Tools)

GMPSignal Real-Time Intelligence MCP (59 Tools)

Official
by xpayrcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

turkey_earthquakes_afad_official_data

Extract real-time Turkey earthquake data from AFAD official feeds, with a configurable result limit for monitoring seismic activity and building structured alerts.

Instructions

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 structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about data source behavior, update frequency, authentication, rate limits, or what 'real-time' means in practice. The phrase 'structured data extraction feed' is too generic to inform invocation behavior.

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

Conciseness2/5

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

The description is short but largely redundant, repeating the tool name and title in a tautological loop. It is not bloated, but it fails to front-load any useful information because there is no substantive content to front-load.

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

Completeness1/5

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

For a data-feed tool with no annotations and no output schema, the description should explain what data is returned, its scope, and its freshness. Instead it provides only a generic restatement, leaving the agent unable to judge whether this tool fits a given earthquake-data request.

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 the single maxResults parameter is fully documented in the schema. The description adds no meaning beyond the schema, but the baseline is 3 when the schema already covers parameter semantics.

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 ('Turkey Earthquakes - AFAD Official Data') without specifying what the tool actually does beyond a generic 'structured data extraction feed.' It does not distinguish this tool from sibling earthquake tools such as europe_mediterranean_earthquakes_emsc_official_data or earthquake_monitor_usgs_emsc_afad.

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, when not to use it, or which sibling tool to choose for earthquake data. The description provides no context about coverage, freshness, or intended use cases.

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

Deploy Server

Other Tools