Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

agents_remove_file

Remove a file from this agent's private knowledge.

The file itself is not deleted — it's just detached from this agent. Use agents.list_files to find the file_id to remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idYesID of the file to detach (from agents.list_files)
agent_idYesID of the agent to remove the file from
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare destructiveHint=false and readOnlyHint=false, which on its own is ambiguous for a removal operation. The description resolves that ambiguity by explaining the file is not deleted, only detached — genuinely additive context. It doesn't address idempotency (annotations say idempotentHint=false) or what happens when the file isn't attached, leaving a small gap.

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?

Three short sentences, front-loaded with the action and the single most important caveat (non-destructive detach), then the prerequisite. No filler.

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 detach operation with full schema coverage, annotations, and no output schema, the description covers what is needed to call it correctly. Only minor behavior (error on a non-attached file, idempotency) is unaddressed.

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 description coverage is 100%, so all three parameters are already documented in the schema, including file_id's origin. The description reinforces the file_id source but adds no semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Remove a file from this agent's private knowledge') and immediately disambiguates scope by clarifying it is a detach rather than a delete. This distinguishes it from files_delete and agents.delete, which an agent could otherwise confuse it with.

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?

It points to agents.list_files as the way to obtain the file_id, which is a useful workflow hint, but never states when to prefer this over siblings like files_delete, collections_remove_file, or agents.add_file's inverse. Usage is implied rather than contrasted with alternatives.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources