Skip to main content
Glama

attach_evidence

Save verification outputs like test results or command output as evidence files and ledger events, returning an ID to reference in task updates or finalizations.

Instructions

Store verification output (test results, command output, review findings, notes, or links) as a file under .agentpack/evidence/ plus a ledger event, returning an evidence id to reference from task_update_verification, task_finalize, or record_decision. Call for meaningful verification worth preserving; for small tasks prefer one aggregated evidence item over many per-command items. Provide the body inline via content or from a file via path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoFree-form label such as test, command, note, link, or json. Defaults to note; kind json stores the file with a .json extension.
pathNoRepo-relative path to an existing file whose contents become the evidence body (alternative to content).
commandNoCommand that produced the output, stored as metadata.
contentNoInline evidence body. Ignored when path is set.
exitCodeNoExit code of that command, stored as metadata.
Behavior3/5

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

With no annotations, the description carries full burden. It discloses storage location, ledger event, and returned ID, and explains behavior of 'kind' parameter. However, it does not mention potential side effects like file overwriting or size constraints.

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?

Two sentences efficiently convey purpose and usage. Front-loaded with key information. Slightly verbose but overall well-structured.

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?

No output schema, but description mentions the returned evidence ID, fitting into a verification workflow. For a relatively simple tool, it provides sufficient context without gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds value by explaining 'kind' defaults and 'json' extension, clarifying that 'content' is ignored when 'path' is set, and noting that 'command' and 'exitCode' are stored as metadata.

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 stores verification output as a file and ledger event, returning an evidence ID. It specifies content types (test results, command output, etc.) and distinguishes its use from siblings by recommending aggregated evidence for small tasks.

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 clear guidance on when to use (meaningful verification worth preserving) and when to prefer aggregated evidence. Mentions referencing from sibling tools but does not explicitly name alternative tools for different scenarios.

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/ihorponom/agentpack'

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