Skip to main content
Glama

list_contacts

Read-onlyIdempotent

Get a joined view of contacts across BTC, EVM, Solana, and Tron chains with verification of signed data. Filter by chain or label for specific records.

Instructions

Return the joined per-label view across chains. Each row contains the label, addresses keyed by chain, optional notes / tags, the earliest addedAt across the joined entries, and an optional unsigned: true flag (issue #428) when at least one chain entry is unsigned (in-memory only). Strict-fail on tamper (signed disk blobs): any signature failure / anchor mismatch / version rollback throws immediately (CONTACTS_TAMPERED / CONTACTS_ANCHOR_MISMATCH / CONTACTS_VERSION_ROLLBACK) rather than silently dropping rows — agents must surface the failure to the user. Unsigned in-memory entries are merged on top of the verified signed view; signed entries always win on a per-(label, chain) basis. In demo mode, the demo in-memory store is read directly (no signature path); all four chains supported, every row is unsigned: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoIf specified, only verifies + returns entries for that chain. Otherwise returns the joined per-label view across all chains with at least one verified entry.
labelNoFilter to a specific label. Useful for 'show me what we know about Mom' single-record reads.
Behavior5/5

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

Annotations indicate readOnlyHint, idempotentHint, and no destructiveness. The description adds critical behavioral details: tamper detection with specific error codes, unsigned entry merge rules, and demo mode behavior—all beyond what annotations provide.

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 relatively long but well-structured, starting with the main purpose and then detailing columns, error handling, and edge cases. Every sentence adds value, though slight trimming could improve conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description fully explains the return structure (columns like label, addresses, addedAt, unsigned flag) and covers important contexts like tamper behavior, demo mode, and merge semantics. It feels complete for a list operation.

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 has 100% description coverage for both parameters. The description reinforces their usage (e.g., chain filter vs all, label for single-record) but does not add significant new meaning beyond the schema.

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 'Return the joined per-label view across chains' with specific details on columns, error handling, and demo mode. It distinguishes from sibling tools like add_contact, remove_contact, and verify_contacts by focusing on read-only listing.

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 provides clear use cases for optional chain and label filters. It explicitly instructs agents to surface failures on tamper, but does not directly say when not to use this tool versus alternatives like verify_contacts.

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/szhygulin/vaultpilot-mcp'

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