Tools

​

Call a Tool

• Endpoint: /api/tools/call/:server
• Method: POST
• Parameters:
  • :server (string, required): The name of the MCP server.
• Body:
  {
    "toolName": "tool-name",
    "arguments": {
      "param1": "value1",
      "param2": "value2"
    }
  }
  
  • toolName (string, required): The name of the tool to execute. Accepted in either form:
    • The bare upstream tool name (e.g. weather). MCPHub will route it to :server.
    • The fully qualified <server><separator><tool> form (e.g. amap-weather). The separator defaults to - and is configurable via systemConfig.nameSeparator (see System Config API). Use the qualified form when an upstream tool name happens to contain the separator and you need to disambiguate.
  • arguments (object, optional): The arguments to pass to the tool. Defaults to an empty object.
• Response:
  {
    "success": true,
    "data": {
      "content": [
        {
          "type": "text",
          "text": "Tool execution result"
        }
      ],
      "toolName": "tool-name",
      "arguments": {
        "param1": "value1",
        "param2": "value2"
      }
    }
  }
  

curl -X POST "http://localhost:3000/api/tools/call/amap" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "toolName": "amap-maps_weather",
    "arguments": {
      "city": "Beijing"
    }
  }'

• The tool arguments are automatically converted to the proper types based on the tool’s input schema.
• Use the x-session-id header to maintain session state across multiple tool calls if needed.
• This endpoint requires authentication.

​

Alternative: OpenAPI Tool Execution

• GET /api/tools/:serverName/:toolName - For simple tools with query parameters
• POST /api/tools/:serverName/:toolName - For complex tools with JSON body