Skip to main content
Glama

hunter_search

Query network asset mapping data using Qianxin Hunter syntax. Filter results by time, status code, asset type, and custom fields.

Instructions

使用 Qianxin Hunter(奇安信鹰图平台)语法查询网络空间测绘数据(小批量实时查询)。若只关心资产数量,请设置 fields="ip,port,domain",page_size=1。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchYes搜索语法(如 'title="北京"'),程序会自动进行 base64url 编码处理。
pageNo页码,默认为 1。
page_sizeNo每页资产条数,默认为 10。可选:1/10/50/100。
start_timeNo开始时间,格式为 YYYY-MM-DD(超出近30天将扣除积分)。
end_timeNo结束时间,格式为 YYYY-MM-DD(超出近30天将扣除积分)。
is_webNo资产类型,1代表”web资产“,2代表”非web资产“,3代表”全部“,默认"全部"。
status_codeNo状态码列表,以逗号分隔,如”200,401“。
fieldsNo可选返回字段,以逗号分隔(如 "ip,port,domain")。默认为空代表选择权限内所有可导出字段。可选字段枚举: ip,port,domain,ip_tag,url,web_title,is_risk_protocol,protocol,base_protocol,status_code,os,company,number,icp_exception,country,province,city,is_web,isp,as_org,cert_sha256,ssl_certificate,component,asset_tag,updated_at,header,header_server,banner,whois,body,vul_list

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, and the description lacks disclosure of behavioral traits such as rate limits, authentication requirements, or data freshness. It only mentions the query syntax and field optimization.

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?

The description is two sentences, front-loading the core purpose and a practical tip, with no redundant information.

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?

With 8 parameters fully described in schema and an output schema present, the description is adequate but lacks deeper guidance on query construction or edge cases like time range handling.

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 coverage is 100%, so baseline is 3. The description adds a helpful tip about fields and page_size for asset counts, providing some added value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool uses Qianxin Hunter syntax for real-time small batch cyberspace mapping queries, and distinguishes from siblings by noting it is a small batch query versus the batch task tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides guidance on when to use this tool (small batch real-time) and a tip for asset count queries, but does not explicitly state when to use alternatives like the batch task tools.

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/PiggyHurry/hunter-mcp'

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