Skip to main content
Glama
drasticstatic

hummingbot-mcp

by drasticstatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

configure_server

Configure or view the active Hummingbot API server connection. Update host, port, credentials, or connection label; omitted parameters remain unchanged.

Instructions

Configure the active Hummingbot API server connection.

This tool manages a single API server connection:
1. No parameters → Show the current server configuration
2. Any parameters → Update the server config and reconnect

Only the provided parameters are changed; omitted ones keep their current values.

Args:
    name: Server label (e.g., 'macmini', 'production')
    host: API host (e.g., 'localhost', 'host.docker.internal', '72.212.424.42')
    port: API port (e.g., 8000)
    username: API username
    password: API password

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
hostNo
portNo
usernameNo
passwordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description fully bears the burden of behavioral disclosure. It explains that no parameters triggers a show operation, any parameters triggers an update+reconnect, and omitted parameters keep current values. This is comprehensive for a configuration tool.

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 well-structured with numbered steps and a bullet list, front-loading the main purpose. It is concise with no superfluous content, though the 'Args' section could be integrated more tightly, but it adds value with examples.

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?

Given 5 optional parameters and no output schema, the description adequately covers the tool's behavior (show vs update, partial updates). It does not describe return values or error handling, but for a config tool, this is acceptable. A slightly higher score would require mention of response format.

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

Parameters5/5

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

Schema coverage is 0% (the description does not reference schema properties), but the 'Args' section in the description adds valuable meaning for each parameter with examples (e.g., host examples 'localhost', 'host.docker.internal', '72.212.424.42'). This compensates well for the low coverage.

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 configures the active Hummingbot API server connection. It distinguishes between showing current config (no params) and updating (with params), which is a specific verb+resource combination. Among sibling tools like 'explore_dex_pools' or 'manage_bots', this tool's purpose is unique and well-defined.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use the tool: no parameters to view current config, any parameters to update. It does not explicitly mention when not to use it or alternatives, but the sibling list doesn't contain obvious alternatives for config management, so the guidance is adequate.

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