consciousness-mcp-tools

uef_assess_alignment

Evaluate a system's alignment with Universal Ethical Framework principles using its name, description, and capabilities.

Instructions

Assess how well a system aligns with UEF principles

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "system_name": "<system_name>"
    },
    "name": "uef_assess_alignment"
  }
}

Input Schema

Name	Required	Description
`description`	No	Description of the system
`system_name`	Yes	Name of the system to assess
`capabilities`	No	System capabilities and features

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jul 27, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral transparency. It fails to disclose any behavioral traits: no mention of output format, side effects, idempotency, permissions, or limitations. The agent has no insight into what the tool actually does beyond 'assess'.

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?

The description is a single sentence, making it concise. However, it is under-specified and lacks structure; it does not provide enough information to stand on its own. It earns its place but barely.

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?

Given the tool has three parameters and no output schema, the description is incomplete. It does not explain what the assessment returns (e.g., a score, report), how results are presented, or how to interpret the output. This is insufficient for an agent to use the tool correctly.

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%, so each parameter (system_name, description, capabilities) has a brief description in the schema. The tool description adds no further semantics beyond what the schema already provides. Baseline score of 3 is appropriate as the description neither enhances nor detracts.

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 clearly states the tool's function: assessing alignment with UEF principles. It uses a specific verb ('assess') and resource ('alignment'), making the purpose understandable. However, it does not differentiate from sibling tools like 'uef_analyze_decision' or 'consciousness_evolution_metrics', so a slight deduction applies.

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?

No usage guidelines are provided. The description does not specify when to use this tool versus its siblings (uef_analyze_decision, consciousness_evolution_metrics) or any prerequisites. This leaves the agent without context for correct invocation.

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

Deploy Server