Skip to main content
Glama

KWeather Weather

get_point_forecast

Read-only

좌표 한 점의 수치 모델 예보를 받는다. model 은 상품 코드(예: kw-point-gfs, kw-point-ifs, kw-point-l015). 고객의 호출 수 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": {
      "model": "<model>",
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_point_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
modelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data behavior are covered. The description adds genuinely new context — that each call consumes one customer call quota and only successful calls are counted — which is useful billing/rate-limit disclosure. It still says nothing about response shape, units, forecast horizons, or failure behavior, so it stays at a 3 rather than higher.

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

Conciseness5/5

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

Three short sentences, front-loaded with the purpose, then the key parameter hint, then the quota note. No filler or redundancy.

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?

For a simple three-parameter read tool with no output schema, the definition covers purpose, product codes, and quota cost. It falls short on coordinate conventions and on what the returned forecast contains, which an agent would need to consume the result sensibly.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the load; it does clarify that `model` is a product code and supplies three concrete examples, which is real added meaning. However, lat and lon receive no treatment at all (coordinate system, valid ranges, ordering), leaving two of three parameters underexplained.

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 specific verb and resource: retrieve a numerical model forecast for a single point coordinate. This separates it from siblings like search_city/search_region (location lookup) and list_products/describe_product (catalog), though it does not explicitly contrast with get_data, the closest ambiguous sibling.

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?

Usage is implied by the purpose statement (single-point forecast retrieval) and the model code examples hint at product selection, but there is no explicit when-to-use vs. get_data guidance, no prerequisites, and no statement of when this tool is the wrong choice.

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