Skip to main content
Glama

list_exam_climate_spots

Lists climate-related exam locations with names, climate symbols, exam dates, and coordinates, and filters them by climate code such as Cs, BW, or Df.

Instructions

평가원 기후 기출 지점(2022~2026학년도) 목록: 이름, 기후 기호, 출제 시험(연월일), 좌표.

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

Input Schema

NameRequiredDescriptionDefault
codeNo기후 기호로 거르기. 예: 'Cs', 'BW', 'Df'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It usefully discloses the dataset window and the exact fields returned, which implies a read-only lookup, but says nothing about result volume, ordering, or whether the list is paginated or complete.

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?

One compact sentence, front-loaded with the resource and scope, then the returned fields. Nothing is padded, though the field enumeration is dense and unpunctuated in the original.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter list tool with no output schema, the description covers scope and return fields, which is exactly what the agent needs to identify the result shape. Little else is required to invoke it correctly.

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 100% and the single optional 'code' parameter is documented with examples in the schema itself. The description adds no filter semantics, so the baseline of 3 applies.

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 resource ('평가원 기후 기출 지점') and a listing action, and bounds the scope to 2022–2026 academic years while naming the returned fields. It is clear what the tool returns, though it doesn't distinguish itself from the unrelated siblings (list_regions, list_bundled_data, find_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 guidance on when to call this versus the other data-listing tools (find_data, list_bundled_data, list_regions) or on when the dataset is inappropriate. The only usage signal is implicit in the dataset scope.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.