Skip to main content
Glama
christophejlegros-lgtm

ASTRA Unified Research Lab MCP Server

get_acm_score

Fetches the current ACM (consciousness proxy) score from the neuromorphic simulation pipeline to assess the experiment's current consciousness level.

Instructions

Consciousness Assessment (Proxy)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Consciousness Assessment (Proxy)' with no mention of side effects, return values, or operational characteristics, making the tool completely opaque.

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 conciseness. The phrase 'Consciousness Assessment (Proxy)' is a vague label that doesn't earn its place because it provides no actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations or output schema, the description needed to explain the return value and interpretation. It doesn't. The tool's purpose, output, and context are all missing, making it inadequate even for a simple getter.

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 input schema has zero parameters, so schema description coverage is 100% trivially. The description adds no parameter information, but with no parameters, there is nothing to explain. Baseline for 0 params is 4.

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 'Consciousness Assessment (Proxy)' is a noun phrase without a verb, essentially restating the tool's name (get ACM score = consciousness assessment). It adds only the vague qualifier 'Proxy' and fails to specify what action is performed or what the score represents, nor does it distinguish from sibling tools like tcai_metaconsciousness.

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 use this tool versus alternatives. No use cases, prerequisites, or exclusions are mentioned. Among many tcai_* and get_* sibling tools, this description provides no differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/christophejlegros-lgtm/ASTRA-Unified-ResearchLab-MCP-v3.0.1'

If you have feedback or need assistance with the MCP directory API, please join our Discord server