Skip to main content
Glama

FarmTempo

get_weather_analysis_short_term

Read-onlyIdempotent

최근 N일간(기본 3일) 실관측 기상 데이터와 가격 변동을 결합한 단기 분석. scatter plot용 데이터 포인트와 자연어 해석(interpretation) 포함.

Combines recent weather observations with price movements for short-term analysis.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_weather_analysis_short_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
station_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile needs no description support. The description does add one useful behavioral fact beyond annotations: the response includes scatter-plot data points and an `interpretation` field. It says nothing about data freshness, station sourcing, or the cost/latency of the analysis.

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 lookback window and output contents are front-loaded, which is good. However, the definition gives the same content twice, once in Korean and once in English, and the English sentence is a strict subset of the Korean one, so roughly half the text is redundant rather than additive.

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?

An output schema exists, so return values need not be re-explained, and the tool has only two optional parameters, keeping complexity low. The remaining gap is the undocumented `station_id` semantics; for a geographically scoped weather analysis, the agent cannot tell what the station controls or whether the default is a sensible geographic default.

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% for both parameters. The description clarifies `days` (N-day lookback, default 3), but `station_id` — including its default of 108 and what station IDs represent — is left entirely unexplained in both schema and description. With low coverage, the description should compensate for both parameters but only covers one.

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 names a specific verb+resource combination: it combines recent observed weather data with price movements into a short-term analysis, and states the default window (3 days). It is clear what the tool produces (scatter-plot points plus a natural-language `interpretation`), but it never distinguishes itself from the sibling `get_weather_price_correlation`, which sounds like a near-neighbor.

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?

Usage is only implied: the 'short-term' / 'recent N days, default 3' framing signals the time horizon and implicitly contrasts with longer-horizon siblings like `get_seasonal_pattern`, and the 1-7 day cap is visible in the schema. There is no explicit statement of when to choose this tool over `get_weather_price_correlation`, nor any prerequisite or exclusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources