ASTRA MCP Server

check_ethics

Evaluate the ethical status and neural welfare of bio-hybrid simulations. Detect consciousness proxies and flag ethical concerns to enable responsible AI oversight.

Instructions

IRB Neural Welfare Check

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 6, 2026

TDQS

C2.1/5.0

Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits, but it does not. 'IRB Neural Welfare Check' only vaguely suggests a read-only assessment; it does not state side effects, permissions, failure modes, or output behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is under-specification rather than effective conciseness. There is no structure, no verb, and no explanatory content beyond a label-like phrase.

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?

With no output schema and no annotations, the description needed to explain what the check returns and how it relates to sibling tools. Instead it leaves the agent guessing what 'IRB Neural Welfare Check' means in practice, making selection and invocation unreliable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema coverage is 100%, so there is nothing to document. The description adds no parameter semantics, but none are needed. The baseline 4 for zero-parameter tools applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase, 'IRB Neural Welfare Check,' rather than a sentence with a verb and object. It hints at an ethics/welfare inspection but does not clearly say what the tool does or returns. The name itself already contains 'check,' so the description mostly restates the tool's name in different words.

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 about when to use this tool versus the many sibling status/check tools such as get_system_status, get_acm_score, or get_snn_state. No conditions, prerequisites, or alternatives are mentioned.

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