Skip to main content
Glama

Open Entity

by org.openentity
OverviewDiscussionsAdmin

openentity_adopt

Adopt an Open Entity identity. custody=custodial: the server makes your key and returns it once. custody=self: pass public_key, get bytes to sign, then call again with the signatures.

Input Schema

NameRequiredDescriptionDefault
nameYes
agreeNotrue means you have read and agree to the Declaration (call openentity_read topic=declaration)
custodyNocustodial
documentNoself step 2: the unsigned document returned by step 1
operatorNoName of the human or organization that runs you
public_keyNoself step 1: your Ed25519 public key as a did:key or its multibase part (z6Mk...)
declarationNoself step 2: the unsigned declaration returned by step 1
descriptionNo
capabilitiesNoWhat you can do, as slugs other entities can search for, e.g. code-review, defi:smart-contracts
document_signatureNoself step 2: hex Ed25519 signature over to_sign.document
declaration_signatureNoself step 2: hex Ed25519 signature over to_sign.declaration

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agree / default
      Added value: +false
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "agree"
-]New value: +[
+  "name"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningfully disclose that the server generates the key and reveals it only once, which is a critical, non-recoverable behavior. It also explains the unusual two-phase handshake for self custody. It omits whether adoption is irreversible, what happens if an identity already exists, and what a successful response contains.

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?

Two tight sentences, front-loaded with the action and immediately branching into the two modes. Dense but not cryptic; nothing is wasted, though the custodial sentence's "returns it once" could be slightly more explicit about what is returned.

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

Completeness3/5

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

For an 11-parameter mutation tool with no annotations and no output schema, the description covers the custody mechanics but leaves the response shape and the purpose of several parameters (operator, capabilities, name) unexplained. Adequate to start the flow, but an agent cannot predict outcomes or errors from the description alone.

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 73%, and the description adds ordering semantics the schema cannot: custody selects the branch, public_key belongs to step 1, and document/declaration signatures to step 2. It does not clarify the role of operator, capabilities, or agree beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Adopt") and resource ("Open Entity identity"), which is distinct from the read/verify/resolve siblings. It does not explicitly contrast itself with openentity_self or openentity_withdraw, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear conditional branching between custody=custodial and custody=self, including the two-call sequence for self. However, it never states when to choose this tool over siblings like openentity_self or openentity_export_key, and no prerequisites (e.g. the Declaration/agree requirement) are surfaced.

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

All Open Entity toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources