Cdec Ca

Latest

latest

Read-onlyIdempotent

Most recent REAL reading for (station, sensor), looking back three days. CDEC writes -9999 into slots it has no reading for and the current day's trailing hours are routinely unwritten, so this skips those and reports how many missing slots it skipped rather than returning the marker as a number.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sensor`	Yes
`station_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`body`	No	Raw text response from API
`format`	No	Indicates response is plain text (non-JSON)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "sensor": 1,
+    "station_id": "SHA"
+  },
+  {
+    "sensor": 2,
+    "station_id": "ORO"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Response from CDEC API containing latest value or raw text",
+  "properties": {
+    "body": {
+      "description": "Raw text response from API",
+      "type": "string"
+    },
+    "format": {
+      "description": "Indicates response is plain text (non-JSON)",
+      "enum": [
+        "text"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it explains CDEC's -9999 placeholder, unwritten trailing hours, the skip behavior, and that the tool reports the count of skipped slots instead of returning the marker. This is exactly the kind of non-obvious behavior an agent needs to interpret results correctly.

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

Conciseness5/5

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

The description is front-loaded with the core purpose, then adds a necessary caveat about CDEC data quirks. Every sentence earns its place, and the structure helps the agent quickly understand both what the tool does and how to interpret its results.

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 simple two-parameter read-only tool with an output schema, the description is complete enough. It covers the lookback window, the missing-slot behavior, and the output semantics, while annotations cover idempotence and read-only safety.

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

Parameters3/5

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

The description maps the parameters to real-world concepts by saying 'station, sensor', which adds a little beyond the raw schema types. However, it does not explain what sensor numbers mean, what station_id formats are accepted, or provide any value constraints, and schema description coverage is 0%.

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

Purpose4/5

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

The description clearly states the tool returns the most recent real reading for a station and sensor, with a three-day lookback. It conveys the specific resource and result type, though it does not explicitly name sibling alternatives to differentiate itself.

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

Usage Guidelines3/5

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

The intended use case is implied: get the latest valid reading for a station and sensor. However, there is no explicit statement about when to prefer this tool over daily_data or hourly_data, nor any guidance on when not to use it.

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

All Cdec Ca 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.