Skip to main content
Glama

run_transform_map

Executes a Transform Map on an Import Set to load source data into target tables; optionally runs as a background job for long loads.

Instructions

Execute a Transform Map on an Import Set to load data (runs GlideImportSetTransformer server-side; requires WRITE_ENABLED and SCRIPTING_ENABLED)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transform_map_sys_id": "<transform_map_sys_id>",
      "import_set_sys_id": "<import_set_sys_id>"
    },
    "name": "run_transform_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
import_set_sys_idYessys_id of the Import Set containing source data
transform_map_sys_idYessys_id of the Transform Map to run

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. First observedv1.0.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is largely covered. The description adds genuine behavioural context beyond that: the server-side engine actually invoked (GlideImportSetTransformer) and the two instance properties that must be enabled before the call can succeed. It does not warn about duplicate inserts on re-run, which is the main consequence of a non-idempotent load.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence front-loads the action and resource, then tucks the implementation detail and prerequisites into a parenthetical. Nothing is padded and nothing important is buried at the end.

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

Completeness3/5

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

There is no output schema, and the description never indicates what a run returns (records imported/merged/skipped, per-row errors) or what a partial failure looks like. For a write operation that can take longer than 20 seconds, that is a meaningful gap, partly offset by the async handling documented in the schema.

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

Parameters3/5

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

Schema description coverage is 100% and all three parameters are documented in the schema, including the async/get_job polling behaviour. The description adds no parameter-level meaning of its own, so the baseline of 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Execute') plus both operands ('a Transform Map on an Import Set') and the outcome ('load data'), which cleanly separates it from read-side siblings such as get_transform_map and list_transform_maps. It stops short of naming an explicit alternative, so sibling differentiation is inferred rather than stated.

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?

The description gives a hard prerequisite (WRITE_ENABLED and SCRIPTING_ENABLED must be on), which is real usage guidance, but never says when to run this versus fluent_transform or how to decide between the interactive and background paths. The choice of async behaviour is left entirely to the schema.

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