Skip to main content
Glama
Sign In

Cdec Ca

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Reservoirs

reservoirs
Read-onlyIdempotent

Reservoir storage snapshots.

Input Schema

NameRequiredDescriptionDefault
station_idNo

Output Schema

NameRequiredDescriptionDefault
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / value / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
  2. 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"
+}
  3. 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"
+}
  4. First observed

TDQS

C2.4/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 handled. The word 'snapshots' adds a mild point-in-time behavioral implication, but the description does not explain behavior such as defaults, filtering, or what happens when station_id is omitted.

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

Conciseness2/5

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

At three words, the description is under-specified rather than usefully concise. It front-loads a noun phrase but omits essential operational detail, so the brevity costs more value than it saves.

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

Completeness3/5

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

The presence of an output schema and read-only/idempotent annotations reduces the burden on the description. However, the description still lacks station_id semantics, guidance on valid values, and any connection to sibling tools, leaving meaningful gaps for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not mention station_id at all. The agent must infer parameter meaning from the parameter name and examples alone; the description adds nothing beyond the schema.

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

Purpose3/5

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

The description names a specific resource ('reservoir storage snapshots') and implies a read/retrieve operation, but it uses no verb and does not explicitly state what the tool does. It also fails to differentiate this tool from siblings like station_info or daily_data, which could overlap in domain.

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 usage context is provided. The description does not say when to use this tool versus alternatives, does not mention the optional station_id parameter, and gives no guidance about selecting a station or interpreting the snapshot data.

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