fisheries-data
Related Servers
Alternatives to fisheries-data
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables users to ask natural-language questions about fisheries data — catches and landings, fleet economics and employment, fishing effort and capacity, stock assessments, subsidies and survey data — and get answers calculated from that data rather than by the language model. Every number returned comes with a signed, re-runnable calculation record naming the query, dataset and source file behind it.European Union Public 1.2- FlicenseNot gradedqualityDmaintenanceAccess oceanographic and environmental data from 63+ ERDDAP servers worldwide through natural language queries. Search datasets, retrieve metadata, and download scientific data for climate research, marine biology, and coastal management.18-
- AlicenseBqualityCmaintenanceEnables natural language querying of oceanographic data from the NES-LTER API, including CTD profiles, cruise datasets, and station information.10MIT
- FlicenseNot gradedqualityCmaintenanceEnables LLMs to work with Copernicus Marine ocean data through semantic tools for dataset discovery, metadata retrieval, recommendation, validation, point time-series extraction, area statistics, subsetting, and computation without exposing raw API plumbing.-
- AlicenseAqualityCmaintenanceEnables agents to discover and access Norwegian open government data by asking questions in natural language, performing filtered searches, running SPARQL queries, and downloading actual dataset files from publishers.6MIT
- AlicenseAqualityDmaintenanceProvides access to FishBase marine biology data including species information, ecological data, distribution records, and morphological details. Enables species name validation and conversion between common and scientific names through natural language queries.8MIT
TDQS
Scored across 7 tools
Each tool maps to a distinct action/resource: source listing, FishStat species lookup, production query, Barentswatch lice retrieval, and Copernicus search/describe/subset. The only mild adjacency is the two FishStat tools, but search versus production are clearly separated.
Most tools use verb_noun (list/search/describe/subset), but fishstat_production_by_country and barentswatch_lice_by_locality are noun phrases with source prefixes and no verb. This is a readable mixed convention, not chaotic, but it prevents a consistent pattern.
Seven tools cover three distinct data domains (FishStat, Barentswatch, Copernicus), plus source discovery without redundancy. The count is appropriate for a multi-source fisheries data server.
Copernicus is well covered with search/describe/subset, and FishStat covers species lookup plus production by source type. The Barentswatch integration is a single narrow endpoint retrieval, so the overall surface is somewhat thin on that source, but there are no critical dead ends for the advertised workflows.