Skip to main content
Glama

chain_spec

List built-in chain templates, run chain specification verification, and produce scoring reports for validating AI-generated code via automated browser testing.

Instructions

链路规格工具(v1.9.5 起合并 chain_list_templates/chain_spec_run/chain_score_report)。通过 mode 参数区分子模式:list(默认,列出所有内置链路模板)/ run(按链路规格执行业务链路验证)/ score(对 chain_spec_run 结果输出 5 维评分报告)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo链路模式:list(默认,列出所有内置链路模板)/ run(执行链路规格验证)/ score(生成 5 维评分报告)list
nameNo链路名称,可作为 runId 兜底(mode=run 时使用)
runIdNo链路运行 ID。mode=run 不传则自动生成;mode=score 可选,用于标识评分对应的运行
stepsNo链路步骤列表,按顺序执行(mode=run 时使用)
resultNochainResult 的别名(mode=score 时使用)
timeoutNo打开 targetUrl 的超时时间,默认 30000ms(mode=run 时使用)
evidenceNo是否每个成功步骤都采集证据,默认 false(mode=run 时使用)
failFastNo步骤失败后是否立即停止,默认 true(mode=run 时使用)
settleMsNo每步完成后的默认稳定等待时间,默认 300ms(mode=run 时使用)
snapshotNo采集证据时是否保存 DOM 摘要,默认 true(mode=run 时使用)
templateNo内置链路模板名,如 marketplace-purchase、login-basic、credits-balance。指定后自动加载模板的 steps/stateSources/expectations/targetUrl,再用传入参数覆盖(mode=run 时使用)
targetUrlNo执行链路前先打开的页面 URL。指定 template 时可覆盖模板的 targetUrl(mode=run 时使用)
screenshotNo采集证据时是否截图,默认 true(mode=run 时使用)
chainResultNochain_spec_run 的完整返回结果对象(mode=score 时使用)
expectationsNo整条链路最终状态断言(mode=run 时使用)
stateSourcesNo整条链路执行前后要采集并对比的状态源(mode=run 时使用)
finalEvidenceNo链路结束时是否采集最终证据,默认 false(mode=run 时使用)
networkFilterNo网络请求过滤条件(mode=run 时使用)
evidenceOnFailNo失败步骤是否采集证据,默认 true(mode=run 时使用)
failOnRuntimeErrorNo每步出现 Console/PageError/Network 错误时是否判失败,默认 true(mode=run 时使用)
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It describes the three modes but fails to mention any side effects, permissions, or potential destructive actions (e.g., browser navigation in run mode). The description is too brief to cover behavioral aspects adequately.

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 concise sentences, front-loaded with the merge context followed by mode breakdown. Every sentence adds value, and the structure is clear and efficient.

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 the tool's complexity (20 parameters, nested objects, no output schema), the description lacks details on return values or expected outputs, especially for 'run' and 'score' modes. It mentions a scoring report but no specifics. The tool also interacts with browsers but no behavioral context is provided.

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 description coverage is 100%, so the schema already explains all 20 parameters. The description adds value mainly by explaining the mode parameter and its enums, but does not elaborate on other parameters beyond what the schema provides. Baseline score of 3 is appropriate.

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 it is a chain specification tool that integrates three previous tools, and explains the three modes (list, run, score) with specific purposes. It distinguishes from sibling tools like chain_list_templates, chain_spec_run, and chain_score_report by noting the merge.

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

Usage Guidelines5/5

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

The description explicitly tells when to use each mode: list for listing templates, run for executing chain validation, score for generating scoring reports. It also mentions the merge, implying these were separate alternatives, providing clear guidance on tool selection.

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