Skip to main content
Glama

resolve_problem

Resolve ServiceNow problems by recording the root cause and resolution notes, with optional assignee and resolution code.

Instructions

Resolve a problem with root cause and resolution notes (requires WRITE_ENABLED=true)

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": {
      "sys_id": "<sys_id>",
      "root_cause": "<root_cause>",
      "resolution_notes": "<resolution_notes>"
    },
    "name": "resolve_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
sys_idYesSystem ID of the problem
root_causeYesRoot cause of the problem
assigned_toNoAssignee sys_id (the problem model needs one to leave New)
resolution_codeNoResolution code (default fix_applied)
resolution_notesYesHow the problem was resolved

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • addedInput schema / properties / assigned_to
      Added value: +{
      +  "description": "Assignee sys_id (the problem model needs one to leave New)",
      +  "type": "string"
      +}
    • addedInput schema / properties / resolution_code
      Added value: +{
      +  "description": "Resolution code (default fix_applied)",
      +  "type": "string"
      +}
  2. First observedv1.0.2

TDQS

A3.5/5.0
Behavior3/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, so the safety profile is covered by structured data. The description adds the WRITE_ENABLED gate, which is useful context the annotations do not convey. It stops short of saying what state transition occurs (e.g. New to Resolved) or whether the change is reversible.

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?

A single front-loaded sentence with the action first and the operational gate second; nothing is wasted. It is arguably too terse for a mutation tool, but no wording is redundant.

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?

For a mutation tool with no output schema and full parameter documentation, the definition covers the essentials: what it does, required inputs, and the write-enablement prerequisite. The remaining gap is the post-resolution state and side effects, which an agent might want before committing.

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 five parameters, including the assigned_to prerequisite for leaving New and the resolution_code default, are already documented in the schema. The description only restates the two required payload fields, adding no format or validation detail beyond the schema.

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?

Names a specific verb and resource ("Resolve a problem") plus the two payload fields that define the operation, so the action is unmistakable. It does not explicitly differentiate itself from the nearby update_problem or close_* siblings, which keeps it short of a 5.

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 parenthetical states a real precondition (WRITE_ENABLED=true), which is genuine when-to-use guidance. However, it gives no guidance on choosing between resolve_problem and update_problem, nor on when a problem is eligible to be resolved rather than just updated.

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