Skip to main content
Glama

FarmTempo

get_current_weather_alerts

Read-onlyIdempotent

특허 #1 추천 시스템의 사용자 인터페이스 출력. 현재 월에 해당하는 기상 민감 품목별 경보를 자연어 메시지로 반환. AI 에이전트가 그대로 사용자에게 전달 가능한 형태.

action 값 4단계

  • 즉시매입 / 선매입권고 / 정상발주 / 매입지연

Monthly weather alerts for current month, with natural language messages.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description need not restate safety. It adds genuine behavioral context that structured fields lack: output is natural-language text the agent can forward directly, scoped to the current month, and carries one of four action levels. It does not cover message length, language, or what happens when no alert applies.

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 four-level action list is useful and front-loaded, but the patent/internal-system header sentence ('특허 #1 추천 시스템의 사용자 인터페이스 출력') adds nothing for an agent, and the Korean and English summaries duplicate each other.

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 zero params, full annotation coverage, and no output schema, the description carries the remaining burden of describing return values, which it does by naming the four action values and the natural-language format. Gaps remain around empty-state behavior and message language, but it is sufficient to call correctly.

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, so the baseline is 4 and no parameter meaning is required. The description correctly signals that no input is needed by framing the call around the current month only.

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 verb and resource: it returns weather-sensitive product alerts for the current month as natural-language messages. The scope (current month, no inputs) is clear, but it does not distinguish itself from siblings such as get_weather_analysis_short_term by name or behavior.

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?

It implies usage by noting the agent can relay the message to the user verbatim, which is a real usage hint. It gives no explicit when-to-use versus alternatives (e.g., short-term weather analysis), no exclusions, and no prerequisites.

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