Skip to main content
Glama

KWeather Weather

get_data

Read-only

상품 API 를 한 번 불러 데이터를 받는다. product 는 상품 코드(예: kw-shrt1, kw-current, kw-world-r1), code 는 search_region · search_city 로 찾은 코드. 고객의 호출 수 1회로 센다(성공한 호출만).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>"
    },
    "name": "get_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNo
productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, but the description adds non-obvious operational context: the call is counted as exactly one customer call, and only successful calls are billed. That billing/quota disclosure is the kind of behavior an agent cannot infer from the schema or annotations. It does not describe failure modes or response shape.

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?

Three short sentences: what it does, what each parameter means, and the billing note, with no filler. The opening sentence is slightly vague ('데이터를 받는다'), but the structure is front-loaded and efficient.

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?

With no output schema, the description should say something about what the returned product data looks like, and it only says '데이터'. Billing and code sourcing are covered well, so the definition is usable, but the return-value gap is a real omission for a data-fetching tool.

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?

Schema coverage is 0%, so the description must carry the parameter burden, and it does explain both parameters: `product` is a product code with three concrete examples, and `code` is the identifier obtained from search_region/search_city. It adds little about types or formatting, but the meaning of each field is clear.

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?

States a concrete verb and resource: it calls the product API once and returns data, and names concrete product codes (kw-shrt1, kw-current, kw-world-r1). The weak point is that '데이터' never says what is actually returned, and no sibling (describe_product, get_point_forecast) is named as a contrast, so the boundary is only partly drawn.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real routing guidance for the optional parameter: the code value must come from search_region or search_city, which tells the agent to call those tools first. There is no explicit 'use this instead of X' or exclusion statement, so it stops short of full when/when-not coverage.

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