snn_reset
Reset the spiking neural network simulation to its initial state. Use this to clear accumulated data and start a fresh simulation run.
Instructions
Reset SNN Engine
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Reset the spiking neural network simulation to its initial state. Use this to clear accumulated data and start a fresh simulation run.
Reset SNN Engine
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full burden. It only says 'Reset' without indicating whether it is destructive, requires permissions, or changes persistent state. The behavioral impact is undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
At two words, it is extremely concise but lacks structure or front-loading of key details. It could be expanded with a brief sentence without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, no annotations, and no parameters, the description is the only source of context. It completely fails to explain what resetting does, side effects, or return values, making it inadequate for a tool likely with significant impact.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are 0 parameters, so the baseline is 4. The description does not need to add parameter information, and the schema describes all (none).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Reset SNN Engine' clearly states the verb (reset) and resource (SNN Engine), but it does not distinguish from similar sibling tools like 'tcai_reset' or explain what specific aspect of the SNN is reset. It is not a tautology but lacks differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives (e.g., 'snn_step', 'simulation_control', 'tcai_reset'). There is no mention of prerequisites, context, or scenarios for resetting.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.9'
If you have feedback or need assistance with the MCP directory API, please join our Discord server