Skip to main content
Glama
agent-passport-system

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Create Principal Identity

create_principal
Destructive

Create a human or org principal identity for agents with an Ed25519 keypair. Return the public key and one-time private key locally; remote redacts it; replace=true overwrites an existing principal.

Instructions

Create a principal identity (human or org behind agents) with its own Ed25519 keypair, held in this process as the session principal with a new fleet. Returns the full public key, and the full private key once on a local (stdio) server. On a remote server (MCP_TRANSPORT=sse or MCP_REMOTE=1) the private key is redacted, as in generate_keys. If a principal already exists in this process the call is refused unless replace=true, because replacing discards the current principal's private key and fleet from this process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoVerifiable domain (e.g. 'aeoess.com')
replaceNoReplace an existing principal. Discards the current principal's private key and fleet from this process, so save the key first.
display_nameYesHuman-readable name (e.g. 'Tima', 'Acme Corp')
jurisdictionNoLegal jurisdiction (e.g. 'US', 'EU')
contact_channelNoContact method (e.g. 'telegram:@aeoess')
disclosure_levelNoHow much identity to revealpublic

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv8.0.0
    • addedInput schema / properties / replace
      Added value: +{
+  "default": false,
+  "description": "Replace an existing principal. Discards the current principal's private key and fleet from this process, so save the key first.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv4.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Addedv2.8.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it explains that the private key is returned in full only on stdio and redacted on remote transports, that an existing principal blocks the call, and that replace=true destroys the current private key and fleet. This is exactly the kind of destructive-consequence and environment-dependent disclosure the destructiveHint alone cannot convey.

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?

Front-loads the core action and key derivation in the opening sentence, then layers the return/redaction and refusal semantics. Dense and slightly run-on, but nearly every clause carries operational information, so little is wasted.

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?

With no output schema, the description carries the burden of explaining returns, and it does: full public key, full private key on stdio, redacted on remote. Combined with the refusal condition and destruction warning, an agent has everything needed to call this mutation correctly.

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%, so the baseline is 3, but the description adds real meaning: it explains why replace is dangerous ('discards the current principal's private key and fleet') and ties the transport env vars to output behavior. The other four optional identity fields (domain, jurisdiction, etc.) get no description-level elaboration, but the schema documents them.

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?

States a specific verb and resource ('Create a principal identity... with its own Ed25519 keypair') and clarifies what a principal is ('human or org behind agents'), which separates it from adjacent tools like identify or create_agent_context. An agent can tell what the tool produces without opening the schema.

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?

Gives concrete operating conditions: it is refused if a principal already exists unless replace=true, and it notes remote-vs-local behavior. It does not explicitly name an alternative tool or say when to prefer this over siblings such as generate_keys or rotate_key, so it falls short of full when/when-not routing.

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

Deploy Server

Other Tools