Exports a TEE-managed key encrypted to your ephemeral ECIES public key, so you can decrypt and use it locally.
Export a key from TEE. The key material is returned encrypted with your ephemeral public key (ECIES). Generates a local keypair, sends the public key to the server, receives encrypted key, decrypts locally.
| Name | Required | Description | Default |
|---|---|---|---|
| keyCode | Yes | The key code to export |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: key material is returned encrypted via ECIES, the client generates an ephemeral keypair, and decryption happens locally. It doesn't specify auth requirements, rate limits, or whether export is audited/irreversible.
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?
Three efficient sentences that front-load the purpose and follow with the mechanism. No wasted words, though the final sentence is more procedural narrative than decision-relevant.
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 single-param tool with no output schema this is adequate, but given no annotations and the sensitivity of exporting key material, the description leaves gaps around permissions, audit implications, and error behavior.
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?
Schema coverage is 100%, so the schema already documents the single keyCode parameter. The description adds no meaning beyond that baseline.
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?
States a specific verb and resource ('Export a key from TEE') and clearly distinguishes from siblings like import_key, get_key, and keygen. An agent immediately knows this retrieves key material from a TEE.
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?
Provides operational context about how the export happens but doesn't state when to use this tool versus get_key or get_public_key, nor any prerequisites or when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.