Skip to main content
Glama
tedorigawa001

ServiceNow-MCP

by tedorigawa001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_import_set_row

Insert a row into an Import Set staging table (a table extending sys_import_set_row) for later transformation (requires WRITE_ENABLED=true)

Instructions

Insert a row into an Import Set staging table (a table extending sys_import_set_row) for later transformation (requires WRITE_ENABLED=true)

Input Schema

NameRequiredDescriptionDefault
dataYesKey-value pairs for the staging table row
staging_tableYesStaging table name (e.g. "u_import_incident"). Must already exist and extend sys_import_set_row.
import_set_sys_idYessys_id of the Import Set that owns this staging table

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.1
    • addedInput schema / properties / import_set_sys_id
      Added value: +{
+  "description": "sys_id of the Import Set that owns this staging table",
+  "type": "string"
+}
    • changedInput schema / properties / staging_table / description
      Previous value: -"Staging table name (e.g. \"u_import_incident\"). Must already exist."New value: +"Staging table name (e.g. \"u_import_incident\"). Must already exist and extend sys_import_set_row."
    • changedInput schema / required
      Previous value: -[
-  "staging_table",
-  "data"
-]New value: +[
+  "staging_table",
+  "import_set_sys_id",
+  "data"
+]
  2. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world behavior; the description adds a genuinely useful behavioral prerequisite (WRITE_ENABLED=true) and the constraint that the staging table must already exist and extend sys_import_set_row. It does not describe what happens on failure or duplicate inserts, which is a minor gap for a non-idempotent write.

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 compact sentence with the action front-loaded, followed by the table-type detail and the prerequisite. No wasted wording.

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 three-parameter write tool with no output schema, the description covers purpose, target table constraint, and the write-enablement prerequisite, which is enough to invoke it correctly. It could note that no sys_id or result is returned, but the essential call-time context is present.

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 three parameters are already documented in the schema, including the nested 'data' object and the staging_table example. The description adds no syntax or format detail beyond the schema, so the baseline 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 ('Insert a row into an Import Set staging table') plus the table family (sys_import_set_row) and the downstream purpose (later transformation). An agent can distinguish it from list/get import set tools, though it doesn't explicitly name the closest sibling (import_excel_to_import_set) as an alternative.

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 prerequisite '(requires WRITE_ENABLED=true)' gives a useful gating condition, but there is no explicit guidance on when to choose this tool over siblings like import_excel_to_import_set or import_cmdb_data, nor on when-not to use it.

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