Skip to main content
Glama

Ipma Seismic

ipma_seismic
Read-onlyIdempotent

Portugal earthquakes, recent seismic events recorded by IPMA for mainland Portugal + Madeira or for the Azores archipelago. Returns time, magnitude, depth, epicenter region, coordinates, and felt intensity when reported. Covers roughly the last 30 days. Example: ipma_seismic({ area: "azores", min_magnitude: 2 })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "area": "azores",
      "min_magnitude": 2
    },
    "name": "ipma_seismic"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo"mainland" (mainland Portugal + Madeira, default) or "azores".
daysNoHow many days back to include, 1-30 (default 7).
min_magnitudeNoMinimum magnitude filter, e.g. 2.0. Events without a computed magnitude are excluded when set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "area": "azores",
      +    "min_magnitude": 2
      +  },
      +  {
      +    "area": "mainland",
      +    "days": 7
      +  }
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered; the description adds genuine behavioral context beyond that — the ~30-day data retention limit and the exact fields returned, including that felt intensity appears only when reported. It stops short of noting refresh cadence, rate limits, or whether results are sorted.

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

Conciseness5/5

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

Three compact sentences, front-loaded with what the tool returns, followed by coverage window and a concrete example. Nothing is repetitive and every clause carries information.

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

Completeness5/5

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

For a three-parameter read-only tool with no output schema, the description supplies the two things that matter most: the temporal scope of the data (~30 days) and an in-line description of the return payload. An agent has enough to call it correctly without further probing.

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 coverage is 100%, so area, days (1-30, default 7) and min_magnitude are already fully documented in the schema, including the note that magnitude-less events are excluded. The description's example call shows a realistic parameter combination but adds no syntax or edge-case meaning beyond the schema, so the baseline of 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?

States a specific resource and source: recent Portugal earthquakes recorded by IPMA, split by region (mainland Portugal + Madeira vs. Azores archipelago). It also enumerates the returned fields (time, magnitude, depth, epicenter region, coordinates, felt intensity), so an agent can distinguish it from the ipma_forecast / ipma_sea_forecast / ipma_uv_forecast siblings without opening a 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?

Usage is implied rather than stated: the 'roughly last 30 days' window tells the agent when the tool is applicable and the Azores/mainland split hints at which variant to pick, but there is no explicit when-to-use / when-not-to-use guidance or named alternative for longer historical windows.

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.