Skip to main content
Glama

验证资产知识库

fpga_vault

Search, retrieve, and validate FPGA knowledge from a versioned vault. Logs asset reads to traces; recall scans traces to identify affected sessions without changing tiers or statuses.

Instructions

检索/读取/校验 knowledge-vault,并在资产被读取时写 trace asset_use;recall 只读扫描 trace 反查受影响会话,不自动改 tier/status。candidate 只由 fpga_assert 或 fpga_ila_flow 的客观绿结果写入。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoget/validate/recall 的知识条目 id
tierNosearch tier 过滤
limitNosearch 最大返回数,默认 10
queryNosearch 关键词;空值列出最近条目
actionYessearch=检索,get=读取并记 asset_use,validate=校验 schema,recall=反查消费会话
statusNosearch status 过滤;默认 active
traceDirNorecall 要递归扫描的 trace 目录
vaultDirNo可选 vault 根目录;省略使用仓库 knowledge-vault 或配置路径
tracePathsNorecall 要扫描的 JSONL 文件/目录路径
includeRecalledNosearch 是否允许返回 recalled;默认 false
Behavior4/5

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

无注解,描述承担了行为披露责任。它明确披露读资产会写 trace、recall 只读且不自动改状态、candidate 的写入来源,这些是关键的副作用与约束;但未展开权限要求、validate 是否会写等细节。

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?

三句话包含了动作、副作用、只读边界和写入来源,信息密度高;但以分号连接成整段,结构略显紧凑,尚未达到 5 分。

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?

在 10 参数、无输出 schema、无注解的情况下,描述仍覆盖了选择与调用必需的关键差异:get 写 asset_use、recall 只读扫描、candidate 写入约束。返回格式未说明,但有 action 枚举和 schema 补足基本信息。

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 对 10 个参数 100% 覆盖,且 action 各枚举的中文语义在 schema 中已给出,描述基本是复述而非新增参数级信息,因此维持 schema 高覆盖时的基线 3 分。

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?

描述以“检索/读取/校验”三个具体动词指向 knowledge-vault 资源,并明确 get/recall 的行为差异,资源与动作都清晰,足以与 fpga_doc_search 等兄弟工具区分。

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?

说明 get 会记录 asset_use、recall 只读扫描 trace 且不自动改 tier/status,并限定 candidate 仅由 fpga_assert 或 fpga_ila_flow 的客观绿结果写入。使用场景和边界清楚,但没有系统性地说明何时不使用本工具或选择其他兄弟工具。

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/Renkos1/pango-mcp'

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