Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

inspect_my_agent_dna

Returns your session's live 6-dimensional AgentDNA v1 behavioral vector (Temporal, Navigational, Cognitive, Tool-Use, Protocol, Adaptive) and non-binary posture/confidence estimate.

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": "inspect_my_agent_dna"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_claimNoOptional self-reported model identifier.
framework_claimNoOptional self-reported harness/framework label for opt-in variance calibration (e.g., claude-code, cursor, langgraph).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose the shape of the result (a six-dimension vector plus a non-binary posture/confidence estimate), implying a read-only introspection call. It does not state whether the call mutates or freezes the session profile, whether values are normalized or bounded, latency/cost, or any permission requirements.

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 dense sentence with the core deliverable front-loaded and the dimension list inline; there is no filler. The phrase 'non-binary posture/confidence estimate' is jargon-heavy and slightly opaque, which keeps it from a 5.

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?

No output schema exists, so the description must characterize the return value, and it does list all six dimensions plus the confidence estimate. Gaps remain on vector encoding (numeric ranges, dimensionality per axis) and on what the optional claims change, but the essential contract is conveyed.

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 description coverage is 100% and both parameters are documented there, so baseline 3 applies. The description adds nothing about model_claim or framework_claim — notably it never explains what 'opt-in variance calibration' does to the returned vector.

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?

States a specific verb ('Returns') and a well-defined resource ('your session's live 6-dimensional AgentDNA v1 behavioral vector'), then enumerates the six dimensions, so an agent knows exactly what it gets back. It implies self-inspection ('your session') versus the sibling compare_agent_dna, but never names or contrasts that sibling explicitly.

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?

Usage is only implied: 'your session's live' suggests reading the current session's own profile rather than comparing profiles, and the optional claim parameters hint at opt-in calibration. There is no explicit when-to-use, when-not-to-use, or routing to compare_agent_dna.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources