Skip to main content
Glama

KWeather Weather

list_products

Read-onlyIdempotent

부를 수 있는 상품 목록(상품 코드 · 이름 · 조회 단위 · 한 줄 설명 · 부르는 법). category 로 좁힐 수 있다: kma(기상청) · kweather(케이웨더) · external · world · bundle(호출 수 상품). 세지 않는다.

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": "list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds that the payload contains descriptive metadata about each product, but the trailing phrase '세지 않는다' ('does not count') is opaque — it is unclear whether it refers to quota, item counts, or pagination, leaving a behavioral question unanswered.

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?

Two dense sentences with the resource and its fields front-loaded, then the filtering dimension. Every clause carries information except the closing '세지 않는다', which is too cryptic to earn its place without elaboration.

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?

For a one-optional-parameter read tool with no output schema, the description covers what the list contains and the legal filter values, and annotations cover safety. The remaining gap is the meaning of the final clause and confirmation of the no-category default.

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% and has no enum, so the description carries the full burden for the single category parameter — and it does: it enumerates kma, kweather, external, world and bundle with short glosses, giving meaning the schema entirely lacks. It stops short of saying what the default null yields, though '좁힐 수 있다' implies an unfiltered list.

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 concrete resource (list of callable products) and enumerates the fields returned (product code, name, lookup unit, one-line description, how to call), so the verb+resource is unambiguous. It does not explicitly contrast itself with describe_product or get_data, which is the only thing keeping it from a 5.

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 states that results can be narrowed by category and lists the valid category values, which gives practical usage context. However, there is no explicit when-to-use/when-not guidance relative to siblings such as describe_product or get_data, so the agent must infer that this is the discovery step before describing or fetching a specific product.

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