Skip to main content
Glama
Sign In

EDNA — On-Device Human Sensing for AI

by space.openos
OverviewDiscussionsAdmin

edna.id.verify_resume

EDNA ID (production): resume gate — reference-window match (>=0.85), never last-hash alone.

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.verify_resume"
  }
}

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.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose two real behavioral facts: the match threshold is >=0.85, and a last-hash-only match is explicitly insufficient. What it does not disclose is what happens on failure, whether the gate mutates session state, or whether this is a read-only check.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, with no wasted sentences, which is good. But the compression goes too far: the em-dash fragment 'never last-hash alone' is cryptic without context, so brevity trades against understandability.

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 a gate/verification tool with no annotations and no output schema, the description should say what a pass and a fail mean and what the caller should do with the result. Instead it gives only a threshold hint, leaving the semantics of the outcome and the reference window's origin unexplained.

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?

There is a single parameter and schema description coverage is 100%; the schema already explains the session id format, the sensor-bridge/AI-client pairing requirement, and the header/'default' fallback. The description adds nothing about the session parameter, so the 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?

The phrase 'resume gate' plus 'verify_resume' conveys that this checks something about a resumed session, and 'reference-window match (>=0.85)' hints at the acceptance criterion. But the description never states in plain terms what is verified against what (a resume token? a session fingerprint?), so an agent must infer the operation from jargon rather than a clear verb+object statement.

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?

There is no guidance on when to call this versus siblings such as edna_identity_verify or edna.id.integrity, and no preconditions or exclusion conditions are stated. The only implied usage is 'use this to gate a resume', which the agent has to derive from the word 'gate'.

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