Skip to main content
Glama
USDA NASS MCP Server

USDA NASS MCP Server

by kin5

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NASS_ENVNoA flag for telling the MCP server to skip local dev steps
transportNoTransport protocol for the MCP server (streamable-http or stdio)streamable-http
NASS_API_KEYYesYour NASS API key (required)
NASS_MCP_HOSTNoThe host to run the MCP server on0.0.0.0
NASS_MCP_PORTNoThe port to run the MCP server on8000
NASS_MCP_FORMATNoThe format to return data (CSV, JSON, or XML)CSV

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_full_datasetC

Get all available data for a given commodity, location, and time.

Args:
    query: Dictionary with three keys, "commodity", "location", and "time", each with a dictionary of parameter and value pairs.

Returns:
    A string containing the API response data or an error message.
get_db_record_countB

Get the number, or count, of database records of a given commodity for a location and time.

Args:
    query: Dictionary with three keys, "commodity", "location", and "time", each with a dictionary of parameter and value pairs.

Returns:
    A JSON string containing one key, "count", and a value of the number of records or an error message.
get_param_valuesB

Get all possible values of a query parameter by its name.

Args:
    parameter: Dictionary with one key, "param", and a value of the parameter name to get the values for.

Returns:
    A JSON string with the parameter name and all possible values as a list or an error message.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_parameter_namesList of all possible query parameter names
get_operatorsList of operators that can be appended to parameter names in a query

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct purposes: retrieving full data, retrieving only a record count, and discovering parameter values. An agent can easily tell which tool to use for each task.

Naming Consistency5/5

All tool names follow a consistent snake_case get_<object> pattern. The naming is predictable and readable across the entire small tool set.

Tool Count5/5

Three tools are well within the appropriate range for a focused data-query server, and each tool serves a distinct necessary function. There is no obvious redundancy or padding.

Completeness4/5

The surface covers core data retrieval, counting, and parameter-value discovery, but lacks an explicit way to discover parameter names or datasets before querying. This is a minor gap that a knowledgeable agent can work around.