Skip to main content
Glama
worlddebugger

Freqtrade-MCP

by worlddebugger
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

fetch_blacklist

Retrieve the current list of prohibited trading pairs from the Freqtrade cryptocurrency trading bot to avoid restricted assets during automated trading operations.

Instructions

Get the current blacklist of trading pairs.

Parameters: ctx (Context): MCP context object for logging and client access.

Returns: str: Stringified JSON response with blacklist data, or None if failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • __main__.py:147-158 (handler)
    The fetch_blacklist tool handler function that retrieves the current blacklist of trading pairs from the Freqtrade API. It accesses the FtRestClient from the MCP context and calls the blacklist() method to fetch the data, returning it as a stringified JSON response.
    def fetch_blacklist(ctx: Context) -> str:
    """
    Get the current blacklist of trading pairs.
    
    Parameters:
        ctx (Context): MCP context object for logging and client access.
    
    Returns:
        str: Stringified JSON response with blacklist data, or None if failed.
    """
    client: FtRestClient = ctx.request_context.lifespan_context["client"]
    return str(client.blacklist())
  • __main__.py:146-146 (registration)
    The @mcp.tool() decorator registers the fetch_blacklist function as an MCP tool with the FastMCP server instance 'mcp'.
    @mcp.tool()
  • __main__.py:148-155 (schema)
    The docstring defines the tool's input/output schema: accepts a Context parameter and returns a stringified JSON response containing blacklist data.
    """
Get the current blacklist of trading pairs.

Parameters:
    ctx (Context): MCP context object for logging and client access.

Returns:
    str: Stringified JSON response with blacklist data, or None if failed.

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the return value format ('Stringified JSON response') and error case ('None if failed'), which adds some behavioral context. However, it lacks details on permissions, rate limits, side effects, or what 'failed' entails, leaving gaps for a tool that interacts with sensitive data like a blacklist.

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

Conciseness4/5

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

The description is front-loaded with the core purpose in the first sentence, followed by structured sections for parameters and returns. It's efficient with no redundant information, though the parameter section could be omitted since there are no user-facing parameters, making it slightly verbose.

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?

Given 0 parameters and no output schema, the description adequately covers the basics: what it does and the return format. However, for a tool fetching a blacklist (a potentially critical data set), it lacks context on data freshness, structure of the JSON, or error handling specifics, which could hinder an agent's effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description correctly notes there are no user-facing parameters by only listing 'ctx' as an internal MCP object, avoiding unnecessary detail. This aligns with the schema and doesn't introduce confusion.

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 ('Get') and resource ('current blacklist of trading pairs'), making the purpose immediately understandable. It distinguishes itself from siblings like add_blacklist and delete_blacklist by focusing on retrieval rather than modification. However, it doesn't explicitly differentiate from fetch_whitelist in terms of data type beyond 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or compare it to related tools like fetch_whitelist or other fetch_* siblings. The agent must infer usage from the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/worlddebugger/freqtrade-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server