Nebelus

Detach file

detach_file

Destructive

Detach a file from the agent (the uploaded file itself is not deleted).

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>",
      "file_id": "<file_id>"
    },
    "name": "detach_file"
  }
}

Input Schema

Name	Required	Description	Default
`file_id`	Yes	Id of the attached file.
`agent_id`	Yes	Target agent's id (from list_agents / create_agent / get_catalog view=agents).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 14, 2026
- addedInput schema / properties / agent_id / description
```
Added value: +"Target agent's id (from list_agents / create_agent / get_catalog view=agents)."
```
- addedInput schema / properties / file_id / description
```
Added value: +"Id of the attached file."
```
First observedSep 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Although annotations already indicate destructiveHint=true, the description adds value by clarifying that the operation only detaches the file and does not delete the underlying uploaded file. This reduces the perceived destructiveness and correctly sets expectations for the agent. No contradiction with annotations.

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 sentence with no unnecessary wordsienne`, and the key clarification about not deleting the file is naturally included. It is well-structured and front-loaded with the main action.

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?

For a two-parameter tool with annotations already covering the destructive hint, the description is adequate. It could be improved by stating whether the file must be currently attached or by referencing the attach_file counterpart, but it is not critically incomplete.

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?

The schema provides descriptions for both parameters (file_id and agent_id), so with 100% schema coverage the baseline is 3. The description does not add extra meaning beyond what the schema states, but it also does not need to.

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

Purpose5/5

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

The description clearly states the tool's action ('Detach a file') on a specific resource ('from the agent') and includes an important clarifying note that the uploaded file itself is not deleted. This distinguishes it from other detach_* tools, though siblings like detach_ai_tool are differentiated by resource type in the name.

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

Usage Guidelines3/5

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

The description implies usage for detaching a file from an agent, but does not explicitly state when to use it versus other detach_* tools. It also does not mention any prerequisites, such as needing the file to be currently attached, though the schema does provide the required parameters.

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

All Nebelus tools Inspect

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

Need Help?