Skip to main content
Glama

Cdec Ca

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Reservoirs

reservoirs
Read-onlyIdempotent

Reservoir storage snapshots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
station_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / body
      Removed value: -{
-  "description": "Raw text response from API",
-  "type": "string"
-}
    • addedOutput schema / properties / count
      Added value: +{
+  "type": "number"
+}
    • removedOutput schema / properties / format
      Removed value: -{
-  "description": "Indicates response is plain text (non-JSON)",
-  "enum": [
-    "text"
-  ],
-  "type": "string"
-}
    • addedOutput schema / properties / items
      Added value: +{
+  "items": {
+    "properties": {
+      "SENSOR_NUM": {
+        "type": "number"
+      },
+      "dataFlag": {
+        "type": "string"
+      },
+      "date": {
+        "type": "string"
+      },
+      "durCode": {
+        "type": "string"
+      },
+      "obsDate": {
+        "type": "string"
+      },
+      "sensorType": {
+        "type": "string"
+      },
+      "stationId": {
+        "type": "string"
+      },
+      "units": {
+        "type": "string"
+      },
+      "value": {
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "station_id": "SHA"
+  },
+  {
+    "station_id": "ORO"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Response from CDEC API containing reservoir storage snapshots 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"
+}
  3. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the annotations—it does not mention what 'snapshots' means (e.g., time range, latest only, historical series), pagination, or data freshness. It does not contradict the annotations, but it also adds no value beyond them.

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

Conciseness3/5

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

The description is extremely short—three words—so it is concise, but it is under-specified rather than efficiently informative. It front-loads nothing useful because the phrase 'Reservoir storage snapshots' is a fragment, not a complete sentence with a verb.

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

Completeness2/5

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

The tool has one optional parameter, an output schema, and rich annotations, so the baseline burden is moderate. However, the description fails to explain what the tool returns, how station_id filters results, or what 'snapshots' implies about time. An agent cannot confidently select or invoke this tool based on the description alone.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the undocumented station_id parameter. It does not. The description never mentions station_id, what values it accepts, or how it affects results. The examples in the schema (SHA, ORO) hint at station codes, but the description itself provides no parameter meaning.

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

Purpose2/5

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

The description 'Reservoir storage snapshots.' is a noun phrase, not a verb+resource statement. It vaguely suggests the tool returns reservoir storage data but does not state what action it performs (e.g., 'Get', 'List', 'Retrieve') or what the output represents. It does not distinguish itself from siblings like daily_data, hourly_data, or station_info.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. The sibling list includes data-related tools (daily_data, hourly_data, latest, event_data) and station_info, but the description does not explain what makes reservoirs the right choice or when to prefer another tool.

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

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