Skip to main content
Glama
Sign In

EDNA — On-Device Human Sensing for AI

by space.openos
OverviewDiscussionsAdmin

edna_identity_create

EDNA ID (production): seal the device-signed identity anchor — only after edna.id.genesis and ≥3 minutes of full human verification on the Chladni hash chain. The seal is a device-key signature; it can only be created on the user's device (this endpoint validates it).

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": "edna_identity_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoTest session id [a-zA-Z0-9_-]{1,64} — sensor bridge and AI client must use the SAME id. Omit to use the X-EDNA-Session header or the "default" session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 meaningful work: it discloses that the seal is a device-key signature that can only be produced on the user's device and that this endpoint merely validates it. That reframes the call from 'create' to 'validate a client-supplied signature', which is valuable. It omits idempotency, what happens if a seal already exists, and failure behavior for a security-critical operation.

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 effect and immediately followed by the strict precondition. No filler sentences or restated title; every clause carries operational content.

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 one-optional-parameter, no-output-schema tool, the description supplies the critical context: ordering requirements, the human-verification time gate, and the fact that the signature originates on the device. Missing only edge-case behavior (repeat sealing, failure modes), which keeps it from 5.

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 coverage is 100% and the single 'session' parameter is fully documented in the schema, so the description need not explain it. The description adds no meaning about session scoping or bridging beyond what the schema states. Baseline 3 applies.

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 concrete action and object: 'seal the device-signed identity anchor', qualified as production. It indirectly separates itself from siblings by naming edna.id.genesis as the prerequisite that must already have run, though the metaphors ('seal', 'Chladni hash chain') make the exact effect less immediately legible than a plain verb would.

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 a hard precondition: only call after edna.id.genesis and after at least 3 minutes of full human verification. That is a real gating rule an agent can act on. It does not state what to do instead when the condition is unmet (e.g., call edna.id.status or edna_identity_verify), so 4 rather than 5.

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

All EDNA — On-Device Human Sensing for AI 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