Skip to main content
Glama
Sign In

EDNA — On-Device Human Sensing for AI

by space.openos
OverviewDiscussionsAdmin

edna.get_signal_vector

Quantized 16-channel behavioral signal vector of this session.

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

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

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

No annotations are supplied, so the description must carry the full behavioral burden. It does not state that the operation is read-only, whether it is cached or expensive, how session identity is enforced beyond the schema, or how the vector should be interpreted.

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?

The definition is a single front-loaded sentence with no redundant wording. Every term contributes to identifying the returned artifact, even though the result is terse.

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 tool with no output schema, the description should explain what the returned vector contains or how to use it, but it only gives a label. The missing usage context and interpretation guidance leave the agent without enough information to invoke it confidently in context.

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 at 100% coverage. The description mentions 'this session' but adds no syntax, default, or usage detail beyond what the schema already says, so 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?

The description identifies a specific resource—a quantized 16-channel behavioral signal vector—and scopes it to the current session. It does not explain how this artifact differs from sibling retrieval tools such as get_live_brief or get_writing_process, so sibling differentiation is missing.

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 tool, what question it answers, or which alternative to use instead. The sentence merely labels the returned artifact.

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