Skip to main content
Glama
Sign In
ASTRA

ASTRA

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

get_snn_state

Read-onlyIdempotent

Retrieve the current SNN engine state to inspect LIF+STDP simulation status, consciousness proxy metrics, and bio-computing telemetry.

Instructions

SNN Engine State

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered externally. The description adds nothing beyond that — no scope of the state snapshot, no freshness/live-vs-cached semantics, no cost. With the bar lowered by annotations, a 2 reflects zero added context.

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?

Three words are certainly concise and front-loaded, but the phrase is under-specification rather than disciplined brevity — it conveys no information. There is no waste to trim, yet no substance either.

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 parameters, no output schema, and a large sibling set of similarly named state/metrics readers, the description carries the burden of explaining what this state read covers and how it differs from the alternatives. It does none of that, leaving the agent unable to select it confidently.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param tool is 4. The empty schema is self-explanatory.

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 just the tool title restated as a noun phrase ('SNN Engine State'), which is a near-tautology of the name get_snn_state. It never states what the tool actually returns or what 'state' comprises, so an agent cannot distinguish it from get_system_status, get_metrics, np_status, or wm_status.

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?

There is no indication of when this tool should be used, when it should not, or which of the many sibling status/metrics tools is the alternative. The agent is left to guess entirely from the name.

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

Deploy Server

Other Tools