Skip to main content
Glama
Sign In
ASTRA

ASTRA

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

inject_spikes

Deliver spike signals to specified neuron IDs with adjustable strength to stimulate or modulate neural activity in ASTRA simulations.

Instructions

Spike Injection

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "neuronIds": "<neuronIds>"
    },
    "name": "inject_spikes"
  }
}

Input Schema

NameRequiredDescriptionDefault
strengthNo
neuronIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already disclose the key traits: not read-only, not idempotent, not destructive, closed-world. The description adds no behavioral context such as what the strength units mean, how injected spikes persist, or whether the call mutates network state.

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?

It is short, but that brevity reflects under-specification rather than efficient structuring. There is no front-loaded statement of purpose beyond a two-word fragment.

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?

For a mutation tool with no output schema and completely undocumented parameters, the definition is inadequate. An agent has nothing to reason about regarding effects, scope, or return values.

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

Parameters1/5

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

Schema description coverage is 0% and the description says nothing about the two parameters. The meaning of 'strength' (bounded -100..100, default 15) and the expected neuronIds form are entirely undocumented.

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 'Spike Injection', which merely restates the tool name/title. It does not clarify what a spike is, what gets injected, or how this differs from the many simulation/neuron siblings such as np_send_trigger or snn_step.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent cannot tell from this text when injection is appropriate versus stepping the network or sending a trigger.

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