Skip to main content
Glama
drasticstatic

hummingbot-mcp

by drasticstatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

setup_connector

Set up or delete exchange connectors for automated trading with progressive disclosure: list exchanges, show required credentials, select account, and confirm override.

Instructions

Setup or delete an exchange connector for an account with credentials using progressive disclosure.

This tool guides you through the entire process of connecting an exchange with a four-step flow:
1. No parameters → List available exchanges
2. Connector only → Show required credential fields
3. Connector + credentials, no account → Select account from available accounts
4. All parameters → Connect the exchange (with override confirmation if needed)

Delete flow (action="delete"):
1. action="delete" only → List all accounts and their configured connectors
2. action="delete" + connector → Show which accounts have this connector configured
3. action="delete" + connector + account → Delete the credential

Args:
    action: Action to perform. 'setup' (default) to add/update credentials, 'delete' to remove credentials.
    connector: Exchange connector name (e.g., 'binance', 'binance_perpetual'). Leave empty to list available connectors.
    credentials: Credentials object with required fields for the connector. Leave empty to see required fields first.
    account: Account name to add credentials to. If not provided, prompts for account selection.
    confirm_override: Explicit confirmation to override existing connector. Required when connector already exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo
connectorNo
credentialsNo
accountNo
confirm_overrideNo

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?

No annotations are provided, so the description carries full burden. It thoroughly explains the multi-step flow, including override confirmation and the two actions. The behavioral traits (progressive disclosure, error handling via account selection) are well disclosed.

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 bullet points, front-loading the purpose. However, it is somewhat lengthy and repeats information (e.g., the args section echoes the step list). Could be slightly more concise, but still clear.

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 the complexity of the tool (5 parameters, interactive flow) and no output schema, the description covers the process adequately. It lacks information about return values or error handling after each step, but for a setup tool the flow is detailed enough.

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 description coverage is 0%, but the description compensates by explaining each parameter's role in the flow. For example, 'action' is described with its possible values, and 'credentials' is related to required fields. All 5 parameters are covered with context.

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 it is for setting up or deleting exchange connectors with a progressive disclosure approach. It distinguishes between the two flows and provides a specific verb+resource. Compared to sibling tools like configure_server or manage_bots, it uniquely handles exchange connector management.

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 explicit step-by-step guidance for both setup and delete flows, indicating when to use each parameter. It implicitly tells when to use the tool (for connecting an exchange) but does not explicitly state when not to use it or mention alternatives. However, the progressive disclosure is a strong guideline.

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