Skip to main content
Glama

complete_task

Marks a ServiceNow task as complete using its sys_id, with optional closed state and closure notes.

Instructions

Mark a task as complete (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>"
    },
    "name": "complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoClosed state value to use (default: the table's closed-complete state, 3 for most tasks)
sys_idYesSystem ID of the task
close_notesNoOptional closure notes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Closed state value to use (default: the table's closed-complete state, 3 for most tasks)",
      +  "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?

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful piece of context beyond that: the WRITE_ENABLED=true requirement. It says nothing about what side effects accompany completion (state transition, timestamps, notifications) or whether repeated calls are safe, so it is useful but thin.

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 short sentence with the action front-loaded and the prerequisite clearly bracketed. No filler, though the terse phrasing leaves room for a clause about side effects.

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 simple single-record mutation with full schema coverage, annotations covering the safety profile, and no output schema to explain, the description supplies the essential purpose and prerequisite. Only the consequence of completing a task (which fields change) is left unstated, which is a minor gap.

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 are already documented, including the meaning and default of 'state'. The description repeats none of this and adds no extra meaning such as valid state values or the effect of close_notes beyond what the schema states, making the baseline 3 appropriate.

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?

The description states a concrete verb and resource ('Mark a task as complete'), so the agent knows exactly what operation is performed. It does not differentiate itself from nearby siblings such as complete_catalog_task or complete_update_set, which keeps it from 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 only guidance is the parenthetical prerequisite WRITE_ENABLED=true, which tells the agent a precondition but not when to prefer this tool over alternatives or when not to use it. Usage is implied rather than explained.

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