Skip to main content
Glama
Sign In

EDNA — On-Device Human Sensing for AI

by space.openos
OverviewDiscussionsAdmin

edna.get_response_guidance

Adaptive Response Layer (production): overridable mode (FLOW/FOCUS/EXPLORE/EXECUTE/REFLECT) from consented dynamics. The humanness score is NEVER an input.

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_response_guidance"
  }
}

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

B3.4/5.0
Behavior4/5

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

Since no annotations exist, the description is crucial. It defines the operational modes (FLOW/FOCUS/etc.), clarifies its production environment status, and provides a critical input constraint (humanness score exclusion).

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?

The definition is concise, efficiently conveying complex operational status and modes in two sentences. It front-loads the key technical identifiers.

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?

The description covers the operational scope and available modes. While it doesn't explain the implementation details of each mode, it provides enough information for an agent to determine if the tool fits the desired operational profile.

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?

With 100% schema description coverage, the input parameter 'session' is adequately defined by the schema itself. The description adds no functional meaning to the session ID beyond context.

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 mentions 'Adaptive Response Layer' and specific modes, but fails to define what the tool *delivers* or *changes* in relation to its function, making the high-level purpose somewhat abstract.

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

Usage Guidelines3/5

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

It outlines key behavioral constraints, notably that the humanness score is never an input. However, it does not give guidance on *when* to use this guidance over, for example, `edna.get_human_context`.

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