Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_file_from_module

Remove a file from a module by specifying the file ID and module ID. This action deletes the module-file junction without deleting the actual file.

Instructions

Remove a file from a module. Deletes module_files junction entry. 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": {
      "file_id": "<file_id>",
      "module_id": "<module_id>"
    },
    "name": "remove_file_from_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesFile ID to remove
module_idYesModule ID to remove from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses that the action deletes the junction entry (a destructive operation on the association) while clarifying the file itself is unaffected. This adds context beyond the annotations (which mark destructiveHint as false, likely referring to the file). No contradiction.

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?

Two sentences, both immediately relevant. No wasted words. Front-loaded with the primary action.

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

Completeness5/5

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

Given the tool's simplicity (2 parameters, no output schema), the description covers what the tool does and what it does not do. It is complete for an agent to decide when to invoke it.

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% and each parameter's description is already clear. The description does not add additional semantic information beyond what the schema provides. Baseline score of 3 is appropriate.

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?

Description clearly states the tool removes a file from a module by deleting the junction entry, and it explicitly distinguishes that the file itself is not deleted. This differentiates it from sibling tools like 'add_files_to_module' and 'delete_file'.

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 when to use this tool (to remove a file from a module) but does not explicitly state when not to use it or mention alternatives beyond the implication that the file remains. No prerequisites or conditions are given.

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