Your first MCP task

Start with a bounded question

After connecting, ask for a small task that can be explained. You do not need to know table names or write SQL for this example.

Discover which earthquake data is available. Inspect its description and time fields before retrieving up to ten most recent available records from one catalogue. Show the source, period, magnitude and relevant limitations.

What the tools do

The service provides dataset discovery and table descriptions, read-oriented queries and REST endpoint discovery. The client should inspect available content and fields before constructing a query. Correct time meaning and table names should be discovered rather than guessed.

Read the result in context

• Where did the records come from, and which catalogue was selected?
• What do the timestamps mean and what interval is displayed?
• Was the result limited, and are any values missing?
• Is this an actual tool result or only an explanation of how the task could be done?

If nothing is found

Keep an empty result empty. If access is missing or a tool fails, the answer should say so. A failed request is not confirmation that no event occurred. Different catalogues can describe the same event.

Choose a next task

Narrow the question with a fixed interval or bounded area while retaining sources and limitations. For repeatable application integration, the REST API may fit better; for visual exploration, try Maps.