Skip to main content
Glama
podaac

CMR Model Context Protocol

Official
by podaac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_datasetsB

Get a list of datasets form CMR based on keywords.

Args:
    startdate: (Optional) Start date of search request (like "2002" or "2022-03-22")
    stopdate: (Optional) Stop date of search request (like "2002" or "2022-03-22")
    daac: the daac to search, e.g. NSIDC or PODAAC
    keywords: A list of keyword arguments to search collections for.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool has a clear, singular purpose of retrieving datasets from CMR based on search parameters.

Naming Consistency5/5

The single tool name 'get_datasets' follows a clear verb_noun pattern, and there are no other tools to create inconsistency. The naming is straightforward and descriptive.

Tool Count2/5

A single tool is too few for a server named 'CMR Model Context Protocol', which suggests a broader scope for interacting with CMR datasets. This minimal toolset feels thin and incomplete for the apparent domain.

Completeness2/5

The tool surface is severely incomplete for a CMR dataset server. There are obvious gaps: no tools for creating, updating, deleting, or managing datasets, and no support for operations like filtering, sorting, or detailed metadata retrieval beyond basic search.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources