Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

turkey_weather_mgm_official

Read-onlyIdempotent

Turkey Weather Forecast (MGM Official) - 81 Provinces: Real-time structured data extraction feed for Turkey Weather Forecast (MGM Official) - 81 Provinces.

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_weather_mgm_official"
  }
}

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.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only the vague claim 'real-time,' without stating update frequency, geographic granularity (province selection is not even a parameter), or what a record contains — a meaningful gap for an open-world data feed.

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?

It is short, but the single sentence is circular, repeating the same title twice with a colon join. No part is front-loaded with actionable information, so brevity here reflects under-specification rather than economy.

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?

With one optional parameter, rich annotations, and no output schema, the description should at minimum say what data comes back per record and how fresh it is. Neither is provided, leaving an agent unable to predict the response shape of an open-world feed.

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 full schema description coverage, so the schema already carries the meaning and a baseline 3 applies. The description contributes nothing further about result limits or pagination.

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 text restates the tool name and title almost verbatim ('Turkey Weather Forecast (MGM Official) - 81 Provinces ... for Turkey Weather Forecast (MGM Official) - 81 Provinces') rather than describing an action. The only added words, 'real-time structured data extraction feed,' do not specify whether it returns forecasts, current conditions, or alerts.

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

Usage Guidelines2/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, no prerequisites, and no mention of alternatives such as the earthquake or other Turkey data feeds in the sibling list. An agent must infer usage purely from the name.

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