Skip to main content
Glama
sshwsfc
by sshwsfc

get_warnings

Retrieve alarm lists with filters for level, status, device, and time range. Supports pagination and keyword search.

Instructions

查询报警列表,支持按级别、状态、设备、时间范围等过滤

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNo查询过滤条件,例如: {"level": 4, "status": 0, "deviceId": "xxx"}
sortNo排序条件,例如: {"occurTime": -1} 表示按发生时间倒序
limitNo返回数量限制
skipNo跳过数量,用于分页
withCountNo是否返回总数
levelNo报警级别: 1-提示, 2-一般, 3-重要, 4-紧急
statusNo报警状态: 0-未确认, 1-已确认, 2-已恢复, 3-已归档
ruleIdNo规则ID
deviceIdNo设备ID
tagIdNo属性点ID
startTimeNo开始时间戳(毫秒)
endTimeNo结束时间戳(毫秒)
keywordNo关键词搜索
Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as read-only nature, pagination behavior, or data freshness. It only mentions filtering options, leaving important behavioral aspects unclear.

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?

The description is a single sentence that directly states the purpose, but it is too brief and omits necessary context. It could be expanded while remaining concise.

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?

Given 13 parameters, no output schema, and many sibling tools, the description is insufficient. It lacks explanation of output format, pagination, and how this tool differs from similar query tools.

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 descriptions cover all 13 parameters clearly (100% coverage). The description adds no new parameter information beyond listing a few filtering dimensions, so it does not improve upon the schema.

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 clearly states it queries a list of warnings with filtering support, but does not differentiate from sibling tools like get_alarms or get_latest_warnings, which target similar resources.

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 use this tool vs alternatives such as get_alarms, get_archived_warnings, or get_latest_warnings. The description only states capability without context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sshwsfc/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server