Skip to main content
Glama

KWeather Weather

describe_product

Read-onlyIdempotent

상품 하나의 설명 — 무슨 데이터인지, 입력, 응답 필드의 뜻 · 단위, 주의. 세지 않는다.

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

Input Schema

NameRequiredDescriptionDefault
productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so safety is covered. The description adds that the output includes cautions and that the tool does not return counts/values, which is genuinely useful, but it does not state the response shape, whether it errors on unknown products, or how complete the documentation is.

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?

It is short and front-loaded with the resource and the list of things it explains, but the trailing clause "세지 않는다" is terse to the point of ambiguity and reads like a fragment rather than a clear exclusion rule.

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 carries the burden of describing return content, and it does outline the sections (data identity, inputs, field meanings/units, cautions). However, it leaves the input format and the failure behavior unspecified, which is a meaningful gap for a tool an agent would routinely call before other product operations.

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?

There is one required parameter, `product`, at 0% schema description coverage, and the description never says whether it expects an ID, a slug, or a display name. It only says the tool will explain "입력" in its output, which does not disambiguate the value the agent must supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it explains a single product: what the data is, its inputs, the meaning/units of response fields, and cautions. That is a recognizable documentation-lookup purpose, but the verb is nominal ("설명") and it never contrasts itself with siblings like get_data or list_products, so the agent must infer that this returns metadata rather than data.

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?

No explicit when-to-use or when-not-to-use guidance is given. The phrase "세지 않는다" (does not count) hints at a boundary, but it is too opaque to tell the agent whether this tool should be called before fetching data or instead of it, and no alternative tool is named.

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