Tool catalogue

The DataMaker MCP server exposes the tools below. The in-product agent gets these plus tools from any connected servers: the SAP/OData server, the Tosca server, and the code-execution server (see the bottom of this page). For setup, see MCP server.

Note

Tool names and schemas are self-describing. The MCP server announces them on connect, so a client always sees the authoritative list. The tables here track the current datamaker server build.

Read / discovery

Tool	What it does
get_templates	All templates in the active project.
get_template_by_id	Full definition of one template.
get_connections	All connections in the project.
get_connection_by_id	One connection’s details (URL, auth method, never secrets).
get_endpoints	All REST endpoints in the project.
get_endpoint_by_id	One endpoint’s details.
get_scenarios	All scenarios in the project.
get_scenario_by_id	One scenario’s source and metadata.
get_scenario_environment_variables	A scenario’s environment variables.
list_integrations	Connected integrations (auth-bearing systems, e.g. SAP gateways); returns id, name, kind, origin. Use this to get an integration_id before discovering its services.

Create / generate

Tool	What it does
create_template_from_json	Infer fields from a sample JSON object/array and save a template.
create_template_from_csv	Fetch a CSV (e.g. an S3 URL), AI-detect field types, and save a template.
generate_from_id	Generate rows from a template by ID.
save_scenario	Create or update a scenario.

Plans

DataMaker’s Plan mode lets the agent design a reviewable test-data plan before running anything. A plan is the spec that compiles into a runnable scenario, not generated data.

Tool	What it does
create_plan	Save a reviewable plan (flow, coverage, gaps, entities) the user can open and run.
list_plans	List the plans in the project (id, title, status).
get_plan	Fetch one plan by id, including its full spec.

Utility

Tool	What it does
ask_user	Ask a clarifying question rendered as clickable choices; used when a required identifier is ambiguous.
flatten_json	Flatten a nested JSON object so nested keys join with dots ({user:{name}} → {"user.name"}).

Tools from connected servers

The in-product agent also loads tools from separate MCP services registered against each session:

• SAP / OData (datamaker-sap): discover services from $metadata, read entities with $filter, and write back to entity sets (with CSRF handling).
• Tricentis Tosca (datamaker-tosca): read Tosca test-case designs and write test data back into Tosca, for both Tosca Cloud and on-prem Tosca Commander (see the table below).
• Code execution (datamaker-cnt): run the Python a scenario needs.

These tools are provided by their own services, so their exact names and schemas live with those services rather than the core datamaker server. Ask the agent “what tools do you have?” in a chat, or inspect the MCP server’s announced tool list, for the authoritative set in your deployment.

Tosca tools (datamaker-tosca)

Back the agent with a Tricentis Tosca connection. integration_id is optional on the read tools; omit it to auto-select the project’s connected Tosca system.

Tool	What it does
tosca-list-testcases	List the test cases in a connected Tosca system. Works for Cloud and on-prem; pass space to pick a workspace.
tosca-read-testcase-design	Read a test case’s full design (configuration parameters, step folders, module/attribute references, value ranges). The input for data-gap analysis.
tosca-create-testcase	Create a new Tosca Cloud test case from a (modified) design payload. Used to act on a gap analysis.
tosca-onprem-list-workspaces	List the workspaces on an on-prem Tosca Commander system. Needed before querying or writing.
tosca-onprem-query	Run a TQL search and return matching object ids. The on-prem way to locate folders, sheets, and execution lists before reading or writing.
tosca-onprem-create-object	Create a child object (TestSheet, Attribute, Instance, ExecutionList, …) under a parent, optionally setting attributes. The headline DataMaker → Tosca write.
tosca-onprem-add-execution-entry	Add a test case to an on-prem execution list.
tosca-onprem-get-object	Read an on-prem object’s attributes, e.g. to inspect execution-result verdicts after a run.

Example call

{
  "name": "generate_from_id",
  "arguments": { "id": "<template-id>", "count": 25 }
}

The exact argument names and options for every tool are part of the schema the MCP server announces on connect; always trust that over a static list.