tmyTypical Meteorological Year — hourly synthetic year representative of the climate.
| Name | Required | Description | Default |
|---|---|---|---|
| endyear | No | ||
| latitude | Yes | ||
| longitude | Yes | ||
| startyear | No |
| Name | Required | Description | Default |
|---|---|---|---|
| inputs | No | Input parameters echoed back | |
| outputs | No |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "latitude": 40.7128,
+ "longitude": -74.006
+ },
+ {
+ "endyear": 2015,
+ "latitude": 35.6762,
+ "longitude": 139.6503,
+ "startyear": 2005
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "inputs": {
+ "description": "Input parameters echoed back",
+ "type": "object"
+ },
+ "outputs": {
+ "properties": {
+ "hourly": {
+ "description": "Hourly weather data for synthetic year",
+ "items": {
+ "properties": {
+ "G(h)": {
+ "description": "Global irradiance (W/m²)",
+ "type": "number"
+ },
+ "Gb(n)": {
+ "description": "Direct normal irradiance (W/m²)",
+ "type": "number"
+ },
+ "Gd(h)": {
+ "description": "Diffuse irradiance (W/m²)",
+ "type": "number"
+ },
+ "RH": {
+ "description": "Relative humidity (%)",
+ "type": "number"
+ },
+ "T2m": {
+ "description": "Air temperature at 2m (°C)",
+ "type": "number"
+ },
+ "WS10m": {
+ "description": "Wind speed at 10m (m/s)",
+ "type": "number"
+ },
+ "time": {
+ "description": "ISO timestamp",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations thoroughly cover safety (readOnly, idempotent), so the description's burden is reduced. It adds that the output is an hourly synthetic year, but lacks details on rate limits, data sources, or limitations.
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 a single phrase, concise but overly terse. It front-loads the resource name but omits essential parameter and usage details, making it under-specified.
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?
Despite having an output schema, the description lacks parameter semantics, usage context, and behavioral details, making it incomplete for an agent to use correctly.
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?
With 0% schema description coverage, the description must explain parameters but does not. No mention of latitude/longitude meaning or startyear/endyear time range.
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 identifies the resource as a Typical Meteorological Year, implying generation or retrieval of hourly synthetic climate data. This distinguishes it from sibling tools like monthly_radiation or pv_performance, though the verb is implicit.
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?
No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions.
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.