Skip to main content
Glama

Neuron Toolsets

neuron_toolsets
Idempotent

Neuron's tools come in groups; only some are loaded to save context. Call with action "list" to see every group, then "enable" the ones the task needs (e.g. ["flows"] to build an automation, ["sell"] for products). If a Neuron tool you expect is missing or reported disabled, enable its group here.

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": {
      "action": "<action>"
    },
    "name": "neuron_toolsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
toolsetsNoGroup names for enable/disable, or ["all"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation, and the description usefully adds the context-saving rationale and the 'missing tool → enable group' recovery behavior. However, it leaves key behavioral questions open for a mutation meta-tool: whether enables persist across turns/sessions, whether disabling removes already-loaded tools, and what 'list' returns. Meaningful but partial disclosure beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the grouping model before the workflow and the fallback trigger. The parenthetical examples are load-bearing rather than filler. Minor density in the last sentence but nothing extraneous.

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

Completeness3/5

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

Given no output schema, the description should at least sketch what "list" returns (group names plus loaded state) and describe the scope/persistence of enablement. It covers the recovery path well but omits disable semantics and the effect of enabling on context budget, which are exactly the facts an agent needs before mutating its own tool set.

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?

Schema coverage is 50%: the action enum is self-evident and the toolsets field already carries a description ('Group names for enable/disable, or ["all"]'). The description earns credit for supplying concrete group-name examples ("flows", "sell") and pairing groups with task types, which the schema cannot convey. It still does not say where the valid group list comes from or confirm that "all" bypasses the need to list first.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific mechanism: Neuron tools are grouped, only some groups are loaded to save context, and this tool lists/enables/disables groups. That is clearly distinct from every sibling, which are individual Neuron actions rather than group management. It does not literally say 'this tool manages toolsets' in a single crisp sentence, but the purpose is unambiguous.

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

Usage Guidelines4/5

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

Strong routing guidance: call action "list" first, then "enable" the needed groups, with concrete examples (["flows"], ["sell"]) and an explicit trigger ('if a Neuron tool you expect is missing or reported disabled, enable its group here'). The gap is the "disable" action, which appears in the enum but is never explained in terms of when or why an agent would use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources