Skip to main content
Glama

fluent_transform

Convert ServiceNow XML records from instance tables or local XML files into Fluent source code to support local project migration and review.

Instructions

Convert XML records from the instance (by table) or from local XML files into Fluent source code (now-sdk transform). REQUIRES FLUENT_ENABLED=true and WRITE_ENABLED=true (writes local files).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fluent_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
authNonow-sdk credential alias (optional)
fromNoLocal XML file or folder to transform instead of the instance
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.
forceNoAllow descendant tables without their parent hierarchy
tablesNoTables to transform by hierarchy, e.g. ["sys_script_include"]
directoryNoProject directory (contains package.json). Defaults to the working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description adds genuinely non-redundant context: the write target is local files, not the instance, and two environment flags must be enabled. It does not say whether existing Fluent files are overwritten or how partial failures behave.

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?

Two sentences, zero waste, with the conversion action and both input sources front-loaded before the gating requirements. Nothing is buried or repeated.

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?

No output schema exists, but the tool returns a job_id path that the schema itself documents via `async`, and the description covers inputs, write target, and prerequisites. Only the overwrite/idempotency behavior is left unstated, a minor gap for a file-writing transform.

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 coverage is 100%, so all six parameters are already documented, and the description mostly restates them. Its one real addition is the either/or framing between instance `tables` and the local `from` path, which the schema does not state. Baseline 3 is appropriate given the schema does the heavy lifting.

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 and transformation direction: XML records (from the instance by table, or from local XML files) into Fluent source code, and names the underlying command `now-sdk transform`. An agent can distinguish this from build/pack/download siblings, though no sibling is named explicitly for contrast.

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 two input modes are spelled out clearly (instance tables vs. local `from` path), which gives a solid context for when this tool applies, and the FLUENT_ENABLED/WRITE_ENABLED prerequisites tell the agent when the call will fail. It stops short of naming when-not conditions or pointing at alternatives such as fluent_download.

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