Geo-Insights Environmental Data

List Environmental Parameters

get_parameters

Read-onlyIdempotent

List all 35 available environmental parameters with units and aliases.

Returns parameters with name, display_name, unit_display (human-readable),
unit_ucum (formal UCUM code), definition_url (CF Conventions), and aliases.
Use aliases in the 'parameter' argument of get_latest_readings or
get_readings_history (e.g. "pm25", "temperature", "no2").

No FROST query needed — this is an instant in-memory lookup. Call it to
discover valid parameter names before querying readings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_parameters"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`parameters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 14, 2026

addedOutput schema / $defs

Added value: +{
+  "ParameterInfo": {
+    "properties": {
+      "aliases": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Aliases",
+        "type": "array"
+      },
+      "definition_url": {
+        "title": "Definition Url",
+        "type": "string"
+      },
+      "display_name": {
+        "title": "Display Name",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "unit_display": {
+        "title": "Unit Display",
+        "type": "string"
+      },
+      "unit_ucum": {
+        "title": "Unit Ucum",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "display_name",
+      "unit_display",
+      "unit_ucum",
+      "definition_url",
+      "aliases"
+    ],
+    "title": "ParameterInfo",
+    "type": "object"
+  }
+}

addedOutput schema / properties / parameters

Added value: +{
+  "items": {
+    "$ref": "#/$defs/ParameterInfo"
+  },
+  "title": "Parameters",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "parameters"
+]

changedOutput schema / title

Previous value: -"get_parametersOutput"New value: +"ParametersResult"

First observedNov 14, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: 'No FROST query needed — this is an instant in-memory lookup,' which tells the agent it is cheap and network-free. The enumeration of return fields is somewhat redundant against the existing output schema, keeping this short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then the return shape, then the usage routing — a sensible order with no filler sentences. The return-field list is mildly duplicative given an output schema exists, which is the only thing keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument, read-only lookup with an output schema and full annotation coverage, the description supplies everything needed: what it returns, what it costs, and how to use the result downstream. No gaps remain for an agent deciding whether and how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. Nothing in the description misrepresents the empty argument set, and the note about which aliases to pass to sibling tools adds useful adjacent meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource and scope: 'List all 35 available environmental parameters with units and aliases.' The fixed count and the inclusion of units/aliases distinguish it immediately from the reading-query siblings it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact call-site role: 'Call it to discover valid parameter names before querying readings,' and routes the returned aliases into the 'parameter' argument of get_latest_readings or get_readings_history, with concrete examples ("pm25", "temperature", "no2"). When-to-use and the downstream alternatives are both explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Geo-Insights Environmental Data tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?