Skip to main content
Glama
Sign In

Nebelus

by ai.nebelus.api
OverviewDiscussionsAdmin

Detach sub-agent

detach_sub_agent
Destructive

Unbind a previously attached sub-agent.

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": {
      "agent_id": "<agent_id>",
      "sub_agent_id": "<sub_agent_id>"
    },
    "name": "detach_sub_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesTarget agent's id (from list_agents / create_agent / get_catalog view=agents).
sub_agent_idYesId of the bound sub-agent to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Target agent's id (from list_agents / create_agent / get_catalog view=agents)."
    • addedInput schema / properties / sub_agent_id / description
      Added value: +"Id of the bound sub-agent to remove."
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds no extra context (e.g., side effects, permissions, reversibility) beyond what annotations provide, so it earns minimal credit.

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

Conciseness5/5

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

The description is a single, succinct sentence with no wasted words. It front-loads the action and object, making it immediately scannable for an agent.

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

Completeness4/5

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

For a simple two-parameter tool with destructive annotations and no output schema, the description is sufficient to guide correct invocation. It could mention the prerequisite that the sub-agent is currently attached, but that is reasonably implied by 'previously attached.'

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 100% with clear descriptions for both agent_id and sub_agent_id. The tool description itself adds no parameter-specific meaning, so it meets the baseline for schema-heavy documentation without extra compensation.

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 clearly states the action (unbind) and the resource (sub-agent), distinguishing it from other detach_* tools by the specific object type. It is concise and unambiguous, though it does not explicitly name sibling tools for differentiation.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives, such as detach_file or detach_vector_store. It only implies the resource type, relying on the agent to infer that this is the correct tool for removing a sub-agent binding.

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

All Nebelus toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources