Skip to main content
Glama

FarmTempo

get_weather_price_correlation

Read-onlyIdempotent

특허 #1 기상×가격 매입 타이밍 추천 시스템의 핵심 데이터. 11년치(2015~2025) KAMIS 가격 + 기상청 ASOS 데이터로 산출한 품목별·월별 피어슨 상관계수 매트릭스.

핵심 필드

  • yearly_corr[품목][기상변수]: {r, p, n, significant} 객체

    • r: 피어슨 상관계수 (-1 ~ +1)

    • p: p-value (0.05 미만이면 통계적 유의)

    • significant: p<0.05 + |r|>=0.7 동시 충족

  • alert_triggers: 사전 정의된 경보 규칙 14개

Monthly weather-price Pearson correlation matrix (Patent #1 core data).

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_price_correlation"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a safe, idempotent, read-only lookup, so the safety profile needs no restating. The description adds genuine value by disclosing the payload structure — `yearly_corr[item][weather_var]` with r, p, n and a `significant` flag, plus 14 predefined `alert_triggers` — which matters because there is no output schema. It stops short of saying whether the matrix is a static precomputed snapshot and how the significance threshold is meant to be acted on, so the disclosure is partial rather than rich.

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

Conciseness4/5

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

It is front-loaded with the purpose, then uses a clear headed bullet block for the field semantics, which is the right structure for a no-parameter data tool. The trailing English sentence merely restates the opening line, and the 'Patent #1 core data' framing is promotional rather than informative, so it earns slightly less than full marks.

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

Completeness4/5

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

With no parameters, no output schema, and full annotation coverage, the burden on the description is mostly return-shape and interpretation, and it largely meets that burden by documenting the nested correlation object and the trigger set. What is missing is operational context an agent would want — data freshness, whether results are cached, and rough response size for a full 11-year item × variable matrix.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description does implicitly communicate that the full matrix is returned unconditionally, which is consistent with the empty schema.

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 states a specific resource — a monthly item × weather-variable Pearson correlation matrix derived from 11 years of KAMIS price and KMA ASOS data — so an agent knows exactly what comes back. It does not, however, differentiate itself from plausible siblings like get_seasonal_pattern or get_item_price_history, leaving the agent to infer which one answers a given question.

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?

The only usage hint is the framing that this is 'core data' for a purchase-timing recommendation system, which implies a downstream analytical use but never states when to call this versus alternatives or when it is not appropriate. There are no prerequisites, no exclusions, and no named alternatives despite many correlation-adjacent siblings.

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