Skip to main content
Glama
IBM

IBM watsonx.data MCP Server

Official
by IBM
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

create_prestissimo_engine

Create a Prestissimo engine in watsonx.data with custom or predefined size configurations. Specify coordinator and worker node types and quantities for optimized query processing.

Instructions

Create a new Prestissimo engine in watsonx.data.

EXAMPLE PAYLOAD: { "origin": "native", "display_name": "My-Prestissimo-Engine", "description": "Prestissimo engine for fast queries", "tags": [], "associated_catalogs": [], "configuration": { "size_config": "custom", "coordinator": { "node_type": "starter", "quantity": 1 }, "worker": { "node_type": "starter", "quantity": 1 } } }

Args: origin: "native" display_name: (required) Display name for the engine configuration: (required) Engine configuration with required fields: - size_config: (required) "custom" (recommended) or predefined options (may be supported) - coordinator: (required) {"node_type": typically "starter" or "cache_optimized", "quantity": 1} - worker: (required) {"node_type": typically "starter" or "cache_optimized", "quantity": 1-18 recommended} associated_catalogs: (optional) List of catalog names to associate description: (optional) Engine description 50 characters max engine_id: (optional) Custom engine ID (must match pattern: prestissimo-0 to prestissimo-1000) tags: (optional) Tags for the engine

CUSTOM SIZE CONFIG (RECOMMENDED):

  • Coordinator: 1 node (always), node_type: "starter" or "cache_optimized"

  • Worker: 1-18 nodes (recommended), node_type: "starter" or "cache_optimized"

  • Node types do NOT need to match (e.g., starter coordinator + cache_optimized worker is allowed)

PREDEFINED SIZE CONFIGS: If using predefined configs, exact node types and quantities must match:

  • starter: 1 coordinator + 1 worker (both bx2.48x192)

  • small: 1 coordinator + 3 workers (both ox2.16x128)

  • medium: 1 coordinator + 6 workers (both ox2.16x128)

  • large: 1 coordinator + 12 workers (both ox2.16x128)

Returns: Dict with created engine details including engine_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYes
display_nameYes
configurationYes
associated_catalogsNo
descriptionNo
engine_idNo
tagsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

No annotations provided, so the description carries the full burden. It describes the creation operation, required parameters, configuration constraints (e.g., node types, quantities), and returns engine details. It does not cover auth requirements or rate limits, but provides extensive behavioral context about allowed values and recommendations.

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 a clear opening line, example payload, parameter descriptions, and detailed sections for custom/predefined configs. It is front-loaded but somewhat verbose; however, the length is justified by the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, nested objects, many options), no annotations, and schema coverage 0%, the description is very complete. It covers all parameters, required vs optional, recommended practices, config options, and return format. No major gaps.

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%, so the description must compensate. It does so thoroughly by explaining each parameter, providing an example payload, detailing configuration subfields (size_config, coordinator, worker), defining constraints (e.g., description max 50 chars, engine_id pattern), and differentiating custom vs predefined setups.

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 starts with 'Create a new Prestissimo engine in watsonx.data.' which is a clear verb+resource statement. The name and context differentiate from siblings like create_presto_engine.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., create_presto_engine). The name implies the engine type, but the description does not provide usage context or when-not-to-use. The detailed configuration instructions imply usage for custom setups.

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/IBM/ibm-watsonxdata-mcp-server'

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