Skip to main content
Glama

Details of one seismic event

get_earthquake_details
Read-only

Retrieve the full record for a single seismic event using its SED event ID, such as the ID returned by recent earthquake listings. Use it to inspect one event's complete details.

Instructions

Full record for one seismic event by its SED event ID; pass the event_id returned by get_recent_earthquakes unchanged (a full 'smi:ch.ethz.sed/…' ID; a short ID is also accepted on a best-effort basis).

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_idYesSED event ID, e.g. 'smi:ch.ethz.sed/sc25a/Event/2026nbzmeg'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description is not carrying the safety burden. It adds the useful behavioral note that short IDs are accepted on a best-effort basis, but says nothing about failure behavior for unknown IDs or what the 'full record' contains.

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?

A single sentence with the resource identified up front and the operational guidance appended, with no redundant restatement of the name or title. Every clause adds information the agent did not already have.

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

Completeness4/5

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

For a one-parameter read-only lookup with full schema coverage and no output schema, the description covers what the agent needs in order to call it correctly. The only remaining gap is what the returned record includes, which is minor for a 'full record' fetch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already gives an example value, so the baseline is 3. The description earns a step above by clarifying that the full 'smi:ch.ethz.sed/…' form must be passed unchanged and that a shortened ID also works — meaning the schema example does not.

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 retrieval: 'Full record for one seismic event by its SED event ID', which names both the resource and the lookup key. It also implicitly distinguishes itself from the sibling get_recent_earthquakes by positioning itself as the per-event record rather than the list.

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

Usage Guidelines4/5

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

It gives concrete guidance on where the key comes from ('pass the event_id returned by get_recent_earthquakes unchanged'), routing the agent through the correct sibling. It stops short of stating when not to use it or what to do if the ID is unknown or the lookup fails.

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