Docs/Skills/Meteorite Data Skill

Meteorite Data Skill

Get meteorite landings data

OperationalCredits 2 per callp50 1275msScience

Overview

Meteorites works by retrieving meteorite data from various reliable sources and providing it in a structured format. You can expect accurate and up-to-date information.

Live Test Meteorite Data Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as MeteoriteDataSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call
{
  "name": "MeteoriteDataSkill",
  "arguments": {
    "name": "Allende"
  }
}

You do not name the tool yourself; the model picks it. Asking about Allende in the terms this skill covers is enough for it to reach for MeteoriteDataSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
nameRequiredstringThe name of the meteorite you want to search for
massOptionalnumberMinimum mass of the meteorite in grams
yearOptionalPremiumnumberThe year the meteorite fell to Earth

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "count": 1,
    "filteredOn": [
      "name"
    ],
    "meteors": [
      {
        "name": "Allende",
        "recclass": "CV3",
        "mass": "2000000",
        "year": "1969",
        "geolocation": {
          "type": "Point",
          "coordinates": [
            -105.31667,
            26.96667
          ]
        }
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
countnumber1Number of meteorites returned in meteors (capped at 30)
filteredOnarray["name"]Array of field names used to filter the meteorite results
meteorsarray[1]Array of meteorite objects matching the search query
meteors.0.namestringAllendeOfficial name of the meteorite specimen
meteors.0.recclassstringCV3Meteorite classification code (composition and type)
meteors.0.massstring2000000Mass of the meteorite in grams as string
meteors.0.yearstring1969Year the meteorite fell to Earth as string
meteors.0.geolocationPremiumobject{…}GeoJSON object with landing site coordinates
meteors.0.geolocation.typePremiumstringPoint
meteors.0.geolocation.coordinatesPremiumarray[-105.31667,26.96667]

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This skill is not part of VerveKit. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Planetarium Exhibit Displays
Museum curators query recorded falls by specimen name to present visitors with the classification, weight, and discovery year of famous space rocks.
Science Coursework Modules
When designing astronomy curricula, educators filter cataloged specimens by mass to illustrate how meteor size distributions vary across recorded recovery events.
Geology Sample Cataloging
To catalog collected specimens, geology labs match field finds against recorded meteorite classifications and known mass thresholds.
Astronomy Reference Portals
Stargazing databases look up historical strike records by name to provide readers with the confirmed weight, type, and fall date of recovered specimens.

Other ways to use Meteorite Data Skill

Set up Meteorite Data Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

More in Science:

Was this page helpful?