Skip to main content
Glama

asset_discovery

Discover frontend routes, API endpoints, and active probes with three modes: routes, enum, and probe. Requires an open browser page.

Instructions

v1.9.5 起合并 asset_routes_discover / asset_endpoint_enum / asset_endpoint_probe 三大资产发现工具。通过 mode 参数切换:routes=前端路由发现;enum=API 端点枚举;probe=端点主动探测。需要先 browser_open 打开页面。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo发现模式:routes=前端路由发现(DOM/hash/JS bundle 静态分析);enum=API 端点枚举(被动分析);probe=端点主动探测(GET/HEAD 请求)enum
methodNo[probe] 探测方法:HEAD 更快但可能被拦截;GET 更可靠HEAD
timeoutNo[probe] 单个请求超时时间(毫秒)
basePathNo[probe] API 基础路径/api
maxScriptsNo[routes/enum] 最多抓取解析的外部 JS bundle 数量(上限 30),用于控制耗时
includeHiddenNo[probe] 是否包含隐藏端点(如 .env, /admin, /backup 等)
maxConcurrentNo[probe] 最大并发请求数
customEndpointsNo[probe] 自定义探测端点列表
probeCategoriesNo[probe] 探测类别:auth=认证;user=用户;order=订单;config=配置;admin=管理端;system=系统;all=全部
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the prerequisite browser_open but does not disclose error behavior, state side effects, or performance implications. The description does not confirm whether the tool is read-only or destructive.

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 short and front-loaded with version info and mode explanation. It efficiently communicates key information without redundancy.

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 9 parameters and no output schema or annotations, the description lacks coverage of return values, error handling, and overall behavior. It is incomplete for a tool of this complexity.

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%, and the description adds marginal context for the mode parameter by listing the three modes. However, it does not significantly enhance understanding beyond what the schema already provides.

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 is a merged version of three asset discovery tools and explains each mode (routes, enum, probe) with specific verbs and resources. It distinguishes itself from siblings by being a consolidated tool.

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?

The description explicitly requires prior browser_open and differentiates the three modes with usage scenarios. However, it does not explicitly mention when not to use or acknowledge that sibling tools like asset_routes_discover may now be redundant.

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/validpilot/ai-verify-mcp'

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