Skip to main content
Glama

get_earthquake_details

Read-onlyIdempotent

Retrieve complete details for a specific seismic event using its SED event ID, so you can inspect earthquake data from Swiss sources.

Instructions

Full details of one seismic event by SED event ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "get_earthquake_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesFrom the other earthquake tools, e.g. smi:ch.ethz.sed/sc25a/Event/2026errxzt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / event_id / description
      Previous value: -"The SED event ID (e.g. 'smi:ch.ethz.sed/sc25a/Event/2026errxzt'). Obtain from get_recent_earthquakes or search_earthquakes_by_location."New value: +"From the other earthquake tools, e.g. smi:ch.ethz.sed/sc25a/Event/2026errxzt"
  2. First observed

TDQS

B3.4/5.0
Behavior3/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 and the description carries a light burden. 'Full details' adds the notion of a complete single-record retrieval rather than a summary, but the description says nothing about what fields come back or what happens with an unknown/expired event ID.

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?

A single front-loaded phrase with no wasted words; the scope ('one seismic event') comes before the identifier requirement. It is a fragment rather than a full sentence, which slightly limits readability but costs nothing in length.

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

Completeness3/5

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

This is a simple one-parameter read tool with no output schema, so the baseline requirement is modest. Still, 'full details' is undefined — no indication of whether it includes magnitude, depth, coordinates, or intensity — which leaves an agent unable to predict what it gains over the list tools.

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% and the single parameter is documented with an example value, so the schema does the heavy lifting. The description only restates that the ID is an 'SED event ID', adding marginal framing beyond the field description.

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

Purpose4/5

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

States a specific verb+resource: 'Full details of one seismic event by SED event ID'. The 'one seismic event' scoping does implicitly separate it from list-style siblings such as get_recent_earthquakes, but it never names those siblings explicitly, so differentiation is inferential rather than stated.

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 only implied: an agent can infer it should call this after obtaining an ID from the search/list tools. There is no explicit when-to-use, no when-not-to-use, and no named alternative for retrieving event data other ways.

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