Skip to main content
Glama

Export the public key for third-party verification

export_public_key
Read-only

Returns Vayl's Ed25519 public key in hex so you can verify erasure receipts, attestations, and the signed audit chain without secret key or database access.

Instructions

Return Vayl's Ed25519 public key (hex). Anyone can use it to verify erasure receipts, attestations, and the signed audit chain WITHOUT the secret key or access to the database.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_public_key"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new context — that the key is public, hex-encoded, and usable without the secret key or database access — which tells an agent this is a safe, unauthenticated disclosure. It does not say whether the key rotates or is stable across calls, which matters for verification workflows.

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?

Two sentences, front-loaded with the concrete return value and its format, followed by the purpose. Every clause carries information; nothing is padding.

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?

For a zero-argument read tool with an output schema and safety annotations, the description covers what the key is, its format, and why it can be shared publicly. The only meaningful omission is key lifecycle — whether the value is stable or rotated — which an agent might need for caching or repeated verification.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a parameterless tool is 4. The description does confirm the output encoding (hex), which is helpful even if it belongs more to the return value than to parameters.

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 states a precise verb and resource — "Return Vayl's Ed25519 public key (hex)" — and even names the encoding. It is immediately distinguishable from siblings such as export_memory, verify_receipt, or verify_audit, which perform different actions on different artifacts.

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?

It clearly states the use case: verifying erasure receipts, attestations, and the signed audit chain without the secret key or database access. That gives an agent solid context for when to reach for it, but it stops short of explicitly routing to or excluding alternatives like verify_audit or verify_receipt.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.