# Pascalsun Agenticgeomate MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.pascalsun%2Fagenticgeomate
Registry id: `mcp-registry/io.github.pascalsun/agenticgeomate`
Status: live (checked 2026-11-22T16:47:17.415Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 133
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "pascalsun-agenticgeomate-mcp-server": {
      "type": "http",
      "url": "https://geomate.nlp-tlp.org/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http pascalsun-agenticgeomate-mcp-server https://geomate.nlp-tlp.org/mcp
```

## Tools (92)

- `compare_points`: Use when the user asks to compare two to eight candidate locations. For each point returns the prospectivity score and tier, tenure status, and the counts of ne
- `describe_dataset`: Use to look at one data-library dataset (`dataset_id` from list_datasets) before querying or reusing it. Returns its name, description, visibility, citation, so
- `describe_raster`: Use to see what a raster dataset holds before sampling it (`raster_id` from list_datasets or list_geophysics_grids). Returns its size, bands, data type, nodata,
- `document_files`: Use when the user wants to open or download a public document found with search_exploration_reports. Read-only: give the hit's corpus and doc_key; returns the d
- `download_drillholes`: Use when a signed-in user asks for drillhole data as a file: every hole within radius_km (at most 10) of a point, or one hole, as a CSV set (a zip of collars, s
- `download_status`: Use to check on one of the user's own download packages or estimates (the id from estimate_download or prepare_download). Read-only. Returns its state, its prog
- `estimate_download`: Use when the user wants to download the files of public exploration reports and publications, to count the files and their size first. It saves the count as an 
- `export_data`: Use when the user wants a whole data layer as a file (GeoJSON or CSV) for their own analysis. Exports one layer from list_export_layers, optionally clipped to a
- `find_core_scans`: Use when the user asks for drill core scanned by HyLogger (the national NVCL library, as CoreFlagging shows it): holes by name, operator or project (q), around 
- `find_drillhole_intercepts`: Use when the user asks for downhole intercepts ("8 m @ 2.1 g/t Au from 120 m") of an element in the drillholes around a point. They are computed from the compan
- `find_drillholes`: Use when the user asks which drillholes there are in a place or of a company or project (WA open-file and company collars). Filter by a bbox or a point and radi
- `find_on_map`: Use to locate an identifier or a place on the map: a tenement ("E 53/1209"), a WAMEX report ("A12345"), a drillhole id, a map sheet, a place name, or coordinate
- `geothought_add_documents`: Use to add documents to one of the user's projects: `documents` [{corpus, key, title?}] and/or `uploads` (dataset ids of their own files, from geothought_upload
- `geothought_answers`: Use to read a project's answers: for a page of its documents (offset, limit) or one `document` {corpus, key}. Returns each question's answer with the quote, pag
- `geothought_arrange_schema`: Use to turn a set of questions into a schema of a kind: GeoThought's model groups and orders them; nothing is saved. Give `question_ids` of saved questions and/
- `geothought_ask`: Use when the user asks a question about a project's documents in words. GeoThought answers from the project's documents and saved answers. Returns the answer wi
- `geothought_check_schema`: Use to check a schema body before saving it. Returns what is wrong or missing in it (unreachable questions, bad edges, ...). A schema is {kind: mindmap|relation
- `geothought_convert_schema`: Use to turn a schema into another kind (mindmap, relation, thoughtgraph); nothing is saved. Returns the converted schema.
- `geothought_copy_project`: Use to copy a project (the user's or a public one) into a new private project of theirs; uploaded files of another account are left out. Returns the copy's id.
- `geothought_create_project`: Use when the user asks for a new GeoThought project. Creates a private project with a name, the schemas it reads with (refs from geothought_schemas / geothought
- `geothought_delete_project`: Use when the user asks to delete one of their projects, with its document list and its readings. Cannot be undone. Returns the deleted id.
- `geothought_delete_question`: Use when the user asks to delete a saved question from their library. Returns the deleted id.
- `geothought_delete_schema`: Use when the user asks to delete one of their schemas. Projects reading with it keep their answers. Returns the deleted id.
- `geothought_delete_upload`: Use when the user asks to delete one of their files: it is taken out of every project, its answers deleted, and the file moved to their data library's trash. Re
- `geothought_document_sections`: Use to fetch another page of sections of the document taken with geothought_next_document (page 0 is the first). Returns that page's numbered sections and their
- `geothought_draft_schema`: Use when the user describes what they want to find out in documents and needs a schema for it. GeoThought's model drafts one; nothing is saved. kind: mindmap (q
- `geothought_edit_document_details`: Use when the user asks to change the details of one of their own uploaded documents: its title, year, operator or commodity. Only the fields given are changed, 
- `geothought_find_documents`: Use to find documents to add to a project. mode=search: by words (`query`); mode=suggest: documents likely to answer the questions of `schemas` (refs) or of `pr
- `geothought_get_schema`: Use to read a schema's body by its ref (s:<id> for the user's own, t:<id> for a template). Returns the schema.
- `geothought_insights`: Use to summarise a project's answers to one schema. Returns, per question, the counts and values; relations; places and years; a thought graph's routes.
- `geothought_models`: Use to see which models the user can read and ask with (GeoThought's own and any they added on the website). Returns each model's id and name, and which ones th
- `geothought_next_document`: Use during an assistant reading (after geothought_start_agent_reading) to take the next document. Returns `task` and `token` (needed for every call about this d
- `geothought_project`: Use to look at one GeoThought project (the user's own or a public one). Returns its schemas, period, documents (each with its corpus and key; an uploaded file w
- `geothought_projects`: Use when the user asks which GeoThought projects they have. Returns each of the signed-in user's projects: id, name, how many documents, and the schemas (with t
- `geothought_publish_project`: Use only when the user asks to make one of their projects public, or private again. public=true: anyone can then open the project, its documents (including the 
- `geothought_questions`: Use to list the user's saved GeoThought questions (their question library). Returns each question's id, text and answer type.
- `geothought_read_plan`: Use before reading a project to see what it would take. Returns the documents, questions, answers already there and what is left. Optional `schemas` (names) and
- `geothought_reading_status`: Use to check a project's reading. Returns its latest reading's state: documents done, being read and waiting, the reader, and a short reason if it failed.
- `geothought_release_document`: Use to hand a document back unread, e.g. when it is too long to read now; it is offered again later. Returns whether it was released.
- `geothought_remove_documents`: Use to take documents out of a project (`documents` [{corpus, key}], `uploads` ids, or all=true). The files themselves stay. Returns how many were removed and t
- `geothought_save_question`: Use to save a question to the user's library; with `id`, it replaces that saved question. `question` is {text, answer_type: boolean|enum|numeric|date|text|place
- `geothought_save_schema`: Use to save a schema as the user's own (private); with `id`, it replaces that schema of theirs (the projects reading with it follow). Returns its ref (s:<id>) t
- `geothought_schemas`: Use to list the user's own schemas (refs s:<id>). Returns each one's ref, name, kind, visibility and question count.
- `geothought_start_agent_reading`: Use when the user wants this assistant, rather than GeoThought's own model, to read a project's documents and answer its schemas' questions. Queues the document
- `geothought_start_reading`: Use when the user asks GeoThought's own reader to read one of their projects: every document is asked its schemas' questions and the answers are kept with their
- `geothought_stop_reading`: Use when the user asks to stop a project's reading. Documents not yet taken are dropped; answers already saved stay. Returns the reading's final state.
- `geothought_submit_replies`: Use to send the answers for some or all sections of the document being read: `replies` is {"<section number>": {"Q1": {"status": "found", "value": ..., "quote":
- `geothought_templates`: Use to list GeoThought's ready-made schemas (refs t:<id>), which a project can read with as they are. Returns each one's ref, name, kind, description and questi
- `geothought_update_project`: Use to change one of the user's projects: name, description, schemas (refs; replaces the list), corpora, period. Making it public is geothought_publish_project.
- `geothought_uploads`: Use to list the user's own document files (every PDF, Word or PowerPoint file in their data library, however it was uploaded). Returns how far each has been rea
- `get_catalogue_dataset`: Use to read one data catalogue entry by its slug (from search_data_catalogue), e.g. before citing or downloading it. Returns its fields, coverage, period, citat
- `get_core_scan_hole`: Use to read one HyLogger-scanned hole by its key (from find_core_scans). Returns where and what it is, the scanned depth range, logged geology per metre (summar
- `get_dataset_feature`: Use to read one feature of a published data-library layer (`layer_id` and `feature_id` from query_features). Returns all of its attributes and its GeoJSON geome
- `get_download_url`: Use when the user asks to download a dataset's original uploaded file. Returns a short-lived download link. Available to the dataset's owner, and to anyone when
- `get_drillhole_traces`: Use when the user asks for the drillholes in an area with their downhole paths or gold grades. Give a bbox (west/south/east/north) or a point (lon/lat, with rad
- `get_geochem`: Use when the user asks for the assay geochemistry (sample concentrations) around a point. Returns, per sample type (STREA stream sediment, ROCKC rock chip, DRIL
- `get_geology_at_point`: Use when the user asks what the geology is at a point in Western Australia. Returns the GSWA 1:500k unit and its place in its 1:250k sheet's stratigraphic colum
- `get_image`: Use to read the details of an image dataset (`image_id` from list_datasets). Returns its size, format, colour mode and frame count; for the image's owner, also 
- `get_job`: Use to check on a job queued with submit_job. Give its taskId; returns its status (pending, running, done or failed) with the result once done, or a short error
- `get_model_inputs_at_points`: Use when the user asks for the geophysical or structural values the prospectivity model reads at specific points. For up to 25 points returns geophysics (magnet
- `get_outcrop_photos`: Use when the user asks for field photographs of outcrops or rock samples near a point in Western Australia (GSWA's WAROX field database). Returns, for the neare
- `get_place_summary`: Use when the user asks for an overview of a 1:250k map area ('areas'), a geological province ('provinces'), a commodity ('commodities') or a Minedex mine or dep
- `get_wa_library_features`: Use to see what one WA data library layer (a "lib:..." id from search_wa_data_library) holds around a point, e.g. the bedrock units, dykes, heritage places or W
- `inspect_point`: Use when the user asks what is known about the ground around a point in Western Australia: who holds it, what has been mined, found or drilled nearby, and what 
- `inspect_region`: Use when the user asks for an overview of what is inside a rectangular area (a bounding box). Returns counts for the area: tenements (live, pending, dead), mine
- `list_datasets`: Use when the user asks which datasets they can read in the data library: their own uploads, datasets shared with them and datasets published publicly. Optional 
- `list_export_layers`: Use when the user wants to know which data layers export_data can export. Returns each layer with its filters, row cap and whether a bbox is required. The layer
- `list_geophysics_grids`: Use to find a public geophysics or terrain grid to read values from: GA's national gravity, magnetics (TMI, RTP, 1VD...), radiometrics, isostatic residuals, SGT
- `list_sites`: Use when the user asks for a list of known mineral sites, deposits or occurrences. Returns up to 200 sites, each with name, commodity, label, isPositive (whethe
- `list_targets`: Use when the user asks which metals can be scored. Returns the metals the prospectivity model supports.
- `make_drillhole_section`: Use when the user asks for a vertical cross-section through a drillhole. The section runs along the hole's own azimuth (east-west for a vertical hole or one who
- `make_map_link`: Use to give the user a link that opens the public data map (https://geo.nlp-tlp.org/map) on a view that shows an answer. The view can set layers to turn on (map
- `measure_distance_or_area`: Use when the user asks how long a line is or how large an area is. Give points as [[lon, lat], ...]; closed=true reads them as a polygon (the first point need n
- `prepare_download`: Use only after the user has agreed to the size that estimate_download reported, to package those files for the user to download. The package is built in the bac
- `query_features`: Use to read the features or rows of a data-library layer (`layer_id` from describe_dataset), a WA data library layer (`layer_id` "lib:..." from search_wa_data_l
- `read_dataset_document`: Use to read one page of a data-library document (`document_id` from list_datasets or search_dataset_documents; `page` is 1-based). Returns the page's text.
- `sample_raster`: Use to read a raster's values at up to 50 WGS84 points ({lon, lat}). Returns the value of each band at each point; a point outside the raster has no value.
- `score_point`: Use when the user asks how prospective a location in Western Australia is for a metal (Au, Cu, Ni, W, Sn, Co, Ta, Mn). Returns the model's prospectivity score (
- `score_region`: Use when the user asks how prospective an area drawn as a polygon is for a metal. Scores an 8x8 grid of points inside the polygon and returns the median score (
- `score_route`: Use when the user asks how prospective the ground is along a road, track or planned drive. Give the ordered vertices of the route (for example a Mapbox Directio
- `search_data_catalogue`: Use when the user asks what data the platform holds on a subject, or where a dataset comes from and under which licence. Searches the platform's data catalogue 
- `search_dataset_documents`: Use to find words in the PDF documents of the data library that the user can read. Accepts Postgres websearch syntax (quoted phrases, OR, -excluded). Returns ea
- `search_exploration_reports`: Use when the user asks what exploration reports, geological survey publications or research papers say about a topic, place, company or mineral. Read-only full-
- `search_tenement_holders`: Use when the user names a company or project and wants what it holds in Western Australia: its tenements, drillholes and WAMEX reports. A company groups its leg
- `search_wa_data_library`: Use to find a Western Australian open-file dataset from the DMIRS Data and Software Centre (DASC) by its title: about 600 datasets (geology, geophysics compilat
- `sql_describe`: Use before writing a query against a table, to get its column names and types. Geometry columns are EPSG:4326 (lon/lat). `schema` is optional: without it the ta
- `sql_query`: Use when a question needs a custom query over the AgenticGeoMate geoscience database. Runs one read-only SELECT (or WITH/EXPLAIN) and returns the rows. Read-onl
- `sql_tables`: Use before writing SQL, to see which tables exist when a question needs data the other tools do not cover. Returns every queryable table, grouped by schema, wit
- `submit_job`: Use for calls that may take longer than a minute, such as score_region over a large or data-dense area. Queues the named tool with its arguments and returns a t
- `top_prospects`: Use when the user asks where the highest-scoring ground for a metal is across Western Australia. Returns up to `n` spaced-apart cells of the precomputed prospec
- `upload_data`: Use when the user asks to add a file from a public https link to their own data library (the platform downloads it; links to private or internal addresses are r
- `wamex_report_files`: Use when the user wants the files of a WAMEX exploration report. Give an anumber (from inspect_point's reports, the wamex tables, or wamex_meta_* joins); return

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
