看雪山 Kanxueshan

query_peaks

按经纬度查询周边可见雪山及今日日照金山预报（金光时段、0-100 评分、天气因子）。参数 lat/lng: WGS-84 十进制度坐标；date: YYYY-MM-DD，缺省今天。

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "query_peaks"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes
`lng`	Yes
`date`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. The word 'query' implies a read operation, but the description does not confirm read-only behavior, required permissions, rate limits, or error conditions. It does add useful output context (golden light period, 0-100 score, weather factors), which partially compensates.

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?

Two dense sentences: the first front-loads what the tool returns, the second documents the parameters. No filler; every clause earns its place.

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?

An output schema exists, so return values need not be explained, and the description still gives a helpful summary of them. Parameters are fully documented, so the main remaining gap is the absence of when-to-use guidance against siblings.

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%, so the description must compensate, and it does: it specifies lat/lng as WGS-84 decimal degrees (a coordinate-system detail absent from the schema) and date as YYYY-MM-DD with today as the default. All three parameters gain meaning beyond their bare titles.

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 states a clear verb+resource: querying snow mountains visible near given coordinates, plus a golden-hour forecast with a score and weather factors. An agent can tell what the tool returns, though it does not differentiate itself from the siblings forecast_peak or search_peak.

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?

Usage is only implied by the coordinates-based query framing. There is no explicit guidance on when to use this tool versus forecast_peak or search_peak, and no prerequisites or exclusions are stated.

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

All 看雪山 Kanxueshan tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.