Skip to main content
Glama

Check Environment

check_environment
Read-only

지역별 실시간 기상/미세먼지/유증기 위험도 진단 및 필터 관리 권장

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": {
      "location": "<location>"
    },
    "name": "check_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that results are '실시간' (real-time) and region-scoped, implying live external data lookup, but says nothing about the freshness or latency of that data or about how the filter-management recommendation is produced.

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 a single compact phrase with no filler, which is good. But the brevity comes at the cost of specification rather than from efficient structure, and there is no front-loaded statement of what the tool returns or when to call it.

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

Completeness2/5

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

With no output schema, no parameter descriptions, and an open-world live-data dependency, the description should say more about what a diagnosis contains and how it relates to get_hvac_filter_info. As written, an agent knows the topic but not the contract needed to invoke the tool confidently.

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?

Schema description coverage is 0%, so the single 'location' parameter is undocumented in the schema and the description must compensate. It only hints through '지역별' that location is a region identifier; it gives no expected format, granularity, or examples, so a caller must guess how to populate the required field.

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 names concrete resources (weather, fine dust, oil-vapor risk by region) and two actions (diagnose, recommend filter management), which is more specific than the tautological title 'Check Environment'. However, it is not clearly differentiated from the sibling get_hvac_filter_info, which also concerns filters, so an agent cannot confidently pick between them from the text alone.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_hvac_filter_info or search_carsafe. Usage is only implied by the phrase '지역별' (by region), leaving the choice between siblings to inference.

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