Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_table_create

Create a new record in a ServiceNow table by providing a table name and field-value object. Writes only run when the server is started with SN_ALLOW_WRITE=1.

Instructions

Create a new record in a ServiceNow table. This is a write tool. It refuses to run unless the server was started with SN_ALLOW_WRITE=1.

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": {
      "table": "<table>",
      "record": "<record>"
    },
    "name": "sn_table_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name, lowercase letters, digits and underscores only. Example: incident.
recordYesField names and values for the new record. Example: {"short_description": "Printer is down"}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark this as non-read-only and non-destructive, and the description adds genuine context beyond them: the write-mode server flag prerequisite that gates execution. It does not describe what a successful call returns (e.g., the new record's sys_id) or what error surfaces when the flag is absent.

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?

Three short sentences, front-loaded with the action, then the write classification, then the prerequisite. 'This is a write tool' is mildly redundant with 'Create' but reasonably earns its place as a safety emphasis.

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 two-parameter write tool with a free-form nested `record` object and no output schema, the description covers the operation and its execution prerequisite. The main residual gap is that return behavior and failure modes are unstated, which matters slightly more given no output schema exists.

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%, with both `table` and `record` fully documented including examples, so the schema does the heavy lifting. The description adds no extra semantics such as required field expectations or table-name restrictions beyond what the schema states.

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: 'Create a new record in a ServiceNow table.' The create-vs-update distinction against siblings like sn_table_update is inferable from the verb, but the description never names or contrasts those siblings explicitly.

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?

It provides a real usage gate — the server must have been started with SN_ALLOW_WRITE=1 — which tells the agent when the call will be refused. However, there is no guidance on choosing this tool over sn_table_update or sn_apply_plan for bulk changes; usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.