Returns every evidence item owned by the calling account, newest first, as a summary (no full receipt data, call get_evidence for the complete receipt kit on a specific item). Use this to find an evidence_id when the caller only knows a file name, or to check on recent timestamping activity.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | No |
Changes observed during successful MCP inspections.
Output schema / properties / data / items / properties / blockchain_tx_hash / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / data / items / properties / blockchain_tx_hash / typeRemoved value: -[
- "string",
- "null"
-]Output schema / properties / data / items / properties / explorer_url / anyOfAdded value: +[
+ {
+ "format": "uri",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / data / items / properties / explorer_url / formatRemoved value: -"uri"Output schema / properties / data / items / properties / explorer_url / typeRemoved value: -[
- "string",
- "null"
-]Output schema / properties / data / items / properties / file_size / anyOfAdded value: +[
+ {
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / data / items / properties / file_size / typeRemoved value: -[
- "integer",
- "null"
-]Output schema / properties / data / items / properties / mime_type / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / data / items / properties / mime_type / typeRemoved value: -[
- "string",
- "null"
-]Output schema / properties / data / items / properties / origin_channel / anyOfAdded value: +[
+ {
+ "enum": [
+ "mcp_agent"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / data / items / properties / origin_channel / enumRemoved value: -[
- "mcp_agent",
- null
-]Output schema / properties / data / items / properties / origin_channel / typeRemoved value: -[
- "string",
- "null"
-]Output schema / properties / data / items / properties / original_file_name / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / data / items / properties / original_file_name / typeRemoved value: -[
- "string",
- "null"
-]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "items": {
+ "properties": {
+ "blockchain_tx_hash": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "created_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "explorer_url": {
+ "description": "Public block-explorer link for blockchain_tx_hash. Null until the timestamp job has settled on-chain.",
+ "format": "uri",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "file_hash": {
+ "description": "SHA-256 hex digest, 64 characters.",
+ "type": "string"
+ },
+ "file_name": {
+ "type": "string"
+ },
+ "file_size": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "id": {
+ "format": "uuid",
+ "type": "string"
+ },
+ "mime_type": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "origin_channel": {
+ "description": "Set to 'mcp_agent' when this item was created via an MCP agent key; null otherwise (web/mobile channel tracking is not yet implemented. See EVIDENCE_CUSTODY_TRACKING_BLUEPRINT.md).",
+ "enum": [
+ "mcp_agent",
+ null
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "original_file_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "enum": [
+ "pending",
+ "submitted",
+ "failed"
+ ],
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden and discloses important behavior: account scoping, sorting, summary-level output, and exclusion of full receipt data. It could additionally mention pagination or limits, but for a zero-parameter listing tool the behavioral disclosure is strong.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences accomplish everything: primary behavior, format caveat, sibling alternative, and concrete use cases. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter list tool with an output schema present, the description fully covers scope, ordering, output format, and when to choose an alternative. Nothing essential is missing for an agent to decide whether to call it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema description coverage is 100%, so the schema carries no hidden burden. The description adds useful context about what the returned evidence_id enables, which is appropriate given there are no params to document.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Returns') and resource ('every evidence item owned by the calling account'), with clear ordering ('newest first') and format ('summary'). It also explicitly contrasts itself with get_evidence, making sibling differentiation immediate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states when to use this tool: to find an evidence_id when the caller only knows a file name, or to check recent timestamping activity. It also directs users to get_evidence for full receipt data, providing a clear alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.