Skip to main content
Glama

ml_train_change_risk

Train the change risk prediction ML model to improve ServiceNow change risk scoring; optionally run as a background job or dry-run the solution definition.

Instructions

Trigger training of the change risk prediction ML model. [Write]

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": "ml_train_change_risk"
  }
}

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.
dry_runNoResolve the solution definition without submitting a training job (default false)
solution_nameNoML solution name (default auto-detect)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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"
      +}
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "Resolve the solution definition without submitting a training job (default false)",
      +  "type": "boolean"
      +}
  2. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true; the description's '**[Write]**' merely restates that. It adds nothing about whether training replaces an existing model, how long it takes, whether it costs quota, or what permissions are needed — all relevant for a non-idempotent training job.

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?

One sentence, front-loaded with the action and target, with no filler. The '**[Write]**' tag is redundant against the annotations but does not obstruct reading.

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

Completeness2/5

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

For a non-idempotent training trigger with no output schema, the description omits what a successful call produces, what happens to a previously trained model, and typical duration. The async parameter partly compensates for the timing gap, but the overall picture an agent needs before triggering training is not assembled anywhere.

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%, so all three parameters (async, dry_run, solution_name) are already well documented, including the ~20 second auto-switch to a job. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 resource: 'Trigger training of the change risk prediction ML model.' The named model distinguishes it from siblings like ml_train_anomaly_detector and ml_train_incident_classifier, and the predict sibling (ml_predict_change_risk) is implicitly the counterpart. It stops short of explicitly saying how it relates to those alternatives.

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

Usage Guidelines2/5

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

There is no statement of when to train versus predict, no prerequisites (e.g., whether a solution must exist first), and no mention of alternatives. An agent must infer the workflow entirely from the tool name.

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