Skip to main content
Glama

get_earthquake_details

Retrieve comprehensive seismic event information using Swiss Seismological Service event IDs to analyze earthquake details and characteristics.

Instructions

Get full details for a specific seismic event by its SED (Swiss Seismological Service) event ID. Use event IDs returned by get_recent_earthquakes or search_earthquakes_by_location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesThe SED event ID (e.g. 'smi:ch.ethz.sed/sc25a/Event/2026errxzt'). Obtain from get_recent_earthquakes or search_earthquakes_by_location.

Implementation Reference

  • The handler function for the get_earthquake_details tool. It takes an event_id, fetches data from the SED API, parses the response, and returns the earthquake details.
    async function handleGetEarthquakeDetails(
      args: Record<string, string>
    ): Promise<string> {
      const eventId = args.event_id?.trim();
      if (!eventId) {
        throw new Error("event_id is required");
      }
    
      const url = buildUrl(BASE, {
        eventid: eventId,
        format: "text",
      });
    
      const raw = await fetchFdsnText(url);
    
      if (!raw) {
        return JSON.stringify({
          error: "Event not found",
          event_id: eventId,
          source: "Swiss Seismological Service (SED), ETH Zürich",
        });
      }
    
      const events = parseFdsnText(raw);
    
      if (events.length === 0) {
        return JSON.stringify({
          error: "Event not found or could not be parsed",
          event_id: eventId,
          source: "Swiss Seismological Service (SED), ETH Zürich",
        });
      }
    
      return JSON.stringify({
        source: "Swiss Seismological Service (SED), ETH Zürich",
        api: "FDSN Event Web Service — http://arclink.ethz.ch/fdsnws/event/1/",
        event: events[0],
      });
    }
  • The schema definition for get_earthquake_details tool.
    {
      name: "get_earthquake_details",
      description:
        "Get full details for a specific seismic event by its SED (Swiss Seismological Service) event ID. " +
        "Use event IDs returned by get_recent_earthquakes or search_earthquakes_by_location.",
      inputSchema: {
        type: "object",
        required: ["event_id"],
        properties: {
          event_id: {
            type: "string",
            description:
              "The SED event ID (e.g. 'smi:ch.ethz.sed/sc25a/Event/2026errxzt'). " +
              "Obtain from get_recent_earthquakes or search_earthquakes_by_location.",
          },
        },
      },
    },
  • Tool registration/invocation point in the main dispatcher function handleEarthquakes.
    case "get_earthquake_details":
      return handleGetEarthquakeDetails(args as Record<string, string>);
Behavior3/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. It indicates this is a read operation ('Get'), but lacks details on behavioral traits such as rate limits, error handling, or response format. The description adds some context by specifying the source of event IDs, but more behavioral information would be helpful given the absence of annotations.

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?

The description is two sentences with zero waste: the first states the purpose, and the second provides usage guidelines. It is front-loaded with the core functionality and efficiently conveys necessary information without redundancy.

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?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is reasonably complete. It covers purpose and usage well, but lacks details on behavioral aspects like response format or error conditions, which could be beneficial for an agent invoking the tool.

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?

The schema description coverage is 100%, so the schema already documents the event_id parameter with examples and sourcing instructions. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high schema coverage without extra value.

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?

The description clearly states the tool's purpose: 'Get full details for a specific seismic event by its SED event ID.' It specifies the verb ('Get'), resource ('seismic event'), and scope ('full details'), and distinguishes it from siblings like get_recent_earthquakes and search_earthquakes_by_location by indicating it's for detailed information on a single event.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: 'Use event IDs returned by get_recent_earthquakes or search_earthquakes_by_location.' This provides clear guidance on prerequisites and distinguishes it from alternatives that list or search for earthquakes, making it easy for an agent to select correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server