Skip to main content
Glama

Earthquakes with felt reports

felt_reports

Find earthquakes near a location that have citizen 'Did You Feel It' reports, sorted by time with felt counts and intensity. Answers questions like 'did anyone feel a quake near me this week?'

Instructions

Find earthquakes near a location that have 'Did You Feel It' (DYFI) citizen reports. Returns events sorted by time with their felt report counts and maximum reported intensity. Good for 'did anyone feel a quake near San Francisco this week' questions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesCenter latitude of the search circle.
longitudeYesCenter longitude of the search circle.
radius_kmNoSearch radius in kilometers. Default 300.
daysNoHow many days back to look. Default 30.
min_feltNoMinimum number of DYFI felt reports. Default 1.
limitNoMaximum number of events to return. Default 25.
Behavior4/5

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

Without annotations, description carries full burden. It discloses output structure (sorted by time, felt counts, max intensity) and implies a read-only operation. No contradictions, but could mention limits or that results are limited to events with min_felt reports.

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?

Two efficient sentences: first describes function, second gives a concrete example. Front-loaded with verb and resource. No wasted words.

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?

Covers core use case and output. With 6 parameters and no output schema, description explains return fields but could mention pagination or that 'limit' controls maximum results. Still adequate for query 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?

Schema coverage is 100%, so baseline is 3. Description adds overall context but does not provide additional semantics beyond the schema descriptions for each parameter.

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?

Description clearly states 'Find earthquakes near a location that have 'Did You Feel It' (DYFI) citizen reports' with a specific verb and resource. It distinguishes from siblings like 'search_earthquakes' by focusing on felt reports and including an example query.

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?

Provides clear context with an example ('did anyone feel a quake near San Francisco this week'), but does not explicitly state when not to use or compare alternatives like 'get_earthquake' for details on a single event.

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/adamcwade/quake-mcp'

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