BFL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageC | Generate an image using FLUX.1 Kontext model based on a text prompt |
| edit_imageB | Edit an existing image using FLUX.1 Kontext model based on a text prompt |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'edit_image' modifies an existing image, while 'generate_image' creates a new image from scratch. There is no overlap in functionality, making it impossible for an agent to confuse them.
Both tools follow a consistent verb_noun pattern ('edit_image' and 'generate_image'), using the same naming convention and style. The verbs are distinct and appropriately descriptive for their actions.
With only two tools, the server feels thin for an image generation/editing domain. It lacks essential operations like retrieving, listing, or deleting images, and does not cover a complete workflow, making it under-scoped for typical use cases.
The tool surface is severely incomplete for an image-related server. It includes generation and editing but misses critical operations such as retrieving, listing, managing, or deleting images, leaving significant gaps that will hinder agent functionality.