daily_dataDaily data for (station, sensor). CDEC's -9999 missing marker is returned as value: null with missing: true, and the response counts the gaps.
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | ||
| start | Yes | YYYY-MM-DD | |
| sensor | Yes | ||
| station_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Raw text response from API | |
| format | No | Indicates response is plain text (non-JSON) |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "sensor": 1,
+ "start": "2024-01-01",
+ "station_id": "SHA"
+ },
+ {
+ "end": "2024-01-15",
+ "sensor": 2,
+ "start": "2023-06-15",
+ "station_id": "ORO"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "description": "Response from CDEC API containing daily time series data 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes beyond the annotations by disclosing a concrete behavioral trait: CDEC's -9999 missing marker is converted to value: null with missing: true, and the response counts gaps. This is useful operational context that the readOnly/idempotent annotations do not convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. The core resource is stated first, and the second sentence adds a specific data-handling detail that is valuable for correct interpretation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema and annotations cover return values and safety, and the missing-marker behavior is a nice addition. However, with low schema coverage and no usage guidance, an agent still lacks enough context about parameter meanings and when to use this tool versus siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 25% (only start is described), so the description must compensate, but it only identifies station and sensor as the lookup keys. It does not clarify end semantics, sensor meaning, station_id format, or how start/end interact, leaving most parameters under-documented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as daily data for a station and sensor, and the name/title plus 'Daily' differentiates it from siblings like hourly_data and event_data. However, it lacks an explicit verb such as 'retrieves' or 'returns', so it falls short of a top score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to choose this tool over alternatives like hourly_data, event_data, or latest. There are no use-case scenarios, exclusions, or stated conditions that would help an agent route between siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.