Skip to main content
Glama
Sign In

EDNA — On-Device Human Sensing for AI

by space.openos
OverviewDiscussionsAdmin

edna.id.status

EDNA ID (production): chain status + measured identity-confidence curve (99%+ = research target).

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

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
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, and it only partly meets it: '(production)' labels the environment and '99%+ = research target' tells the agent how to interpret the confidence metric, which is genuinely useful. It says nothing about read-only safety, side effects, authentication, the shape of the response, or how the confidence curve is measured or updated.

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?

One compact sentence with the environment qualifier front-loaded and no filler. It is efficient, though the dense jargon ('measured identity-confidence curve', 'research target') takes a moment to parse and could be unpacked slightly.

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 a one-optional-parameter status tool with no output schema and no annotations, the description covers the resource and the metric interpretation but leaves behavioral gaps: unknown return shape, unknown whether session state affects output, and no routing guidance among siblings.

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?

The single optional session parameter is fully documented in the schema (100% coverage), including pattern, shared-id requirement, and header/default fallback behavior. The description adds nothing beyond that, so the baseline 3 for high schema coverage 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 description names the resource ('chain status') and a second output ('measured identity-confidence curve'), so an agent can infer this is a read-only status/metrics endpoint. However, it supplies no verb and does not distinguish itself from close siblings such as edna.id.integrity or edna.id.verify_resume, leaving ambiguity about which status-like tool to pick.

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 explicit when-to-use statement, no prerequisites, and no mention of alternatives. At best, 'chain status' weakly implies 'call this to check status', which is inferable usage rather than guidance; nothing tells the agent when to prefer it over the integrity or verification tools.

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