Skip to main content
Glama
Sign In

EDNA — On-Device Human Sensing for AI

by space.openos
OverviewDiscussionsAdmin

edna.id.export_state

EDNA ID (production): local state export — no private key, no raw signals, no plaintext handle.

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.id.export_state"
  }
}

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

C2.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries full burden. It does add real behavioral value by declaring what the export never contains (private key, raw signals, plaintext handle), which is the key safety property for an export operation. However, it never states whether the tool returns data or writes a local file, whether it mutates state, or whether it is repeatable — the most consequential traits for an unannotated tool.

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?

A single compact sentence fragment with the exclusions front-loaded; nothing is wasted. The unexplained "(production)" qualifier is the only piece of low-value text.

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

Completeness2/5

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

For an export tool with no output schema, the return shape, format, size, and destination of the exported state are entirely undocumented. The description covers only what is withheld, leaving an agent unable to predict what comes back or what side effects occur.

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 optional session parameter is fully documented in the schema, including its regex, the sensor-bridge/client id-matching rule, and header/default fallback. The description adds nothing about session behavior, so baseline 3 applies.

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

Purpose3/5

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

"Local state export" gives a verb and resource, but "state" is never defined — the agent cannot tell what is actually exported (session data? agent memory? config?). The parenthetical "(production)" is unexplained, and the negations describe what is excluded rather than what the output is. It is distinguishable from siblings like edna.id.memory only by the word "export".

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no prerequisites, and no mention of when to prefer a sibling such as edna.id.memory or edna.id.status instead. The only clause resembling guidance is the privacy caveat, which is not usage routing.

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