Skip to main content
Glama
christophejlegros-lgtm

ASTRA — Unified Research Lab + MCP Server

get_snn_state

Retrieve the current state of the SNN engine in the ASTRA neuromorphic simulation pipeline to monitor real-time neural network activity and dynamics.

Instructions

SNN Engine State

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations and a two-word description, the tool's behavior is completely opaque. Whether it is read-only, its side effects, or required permissions are undisclosed.

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?

Extremely brief but lacks substance; it is under-specified rather than concise. The description could be improved with a single clear action verb.

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 output schema and no annotations, the description should elaborate on the returned state. It fails to provide a complete picture for the agent.

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?

There are no parameters and schema coverage is 100%, baseline is 3. The description does not add any meaningful context beyond what the schema already shows.

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?

Description 'SNN Engine State' barely restates the tool name, offering little clarity on its specific purpose. It does not explicitly state that the tool retrieves or returns the state.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus siblings like snn_step or snn_reset. The context and prerequisites are entirely absent.

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-v2.8'

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