Skip to main content
Glama

open_record_form

Read-only

Opens an interactive in-chat form to create or edit ServiceNow records, with default table fields, choice lists, and reference lookups; prefill values, review, and save.

Instructions

Open an interactive form to create or edit a ServiceNow record (incident, change_request, problem, any table) inside the chat. Fields follow the table's default form layout, with choice lists, dependent choices and reference lookups. Omit sys_id to create a new record; pass values to prefill. The user reviews and saves.

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>"
    },
    "name": "open_record_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name, e.g. incident
fieldsNoFields to show instead of the form layout (optional)
sys_idNoRecord to edit. Omit to create a new record.
valuesNoValues to prefill, e.g. {"short_description":"VPN down"}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description is consistent with that – it opens a form and 'The user reviews and saves,' so no direct write is implied. It adds useful behavior beyond annotations: fields follow the table's default form layout with choice lists, dependent choices, and reference lookups. It does not say what happens if the user cancels or what the tool returns, but the interaction model is well conveyed.

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 tight sentences, front-loaded with the core action and followed by the create/edit decision rule and the review outcome. No padding, though a bit of the sys_id/values wording duplicates the schema rather than adding new information.

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

Completeness3/5

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

For an interactive, human-in-the-loop tool with no output schema, the definition leaves open what the agent receives after the form is saved or cancelled, and whether the call blocks. The form-layout and prefill behavior is covered well, but return/termination semantics are missing.

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%, and the description largely restates schema text ('Omit sys_id to create', 'pass values to prefill'). It does add meaning for 'fields' by explaining that the default is the table's form layout with choice lists and reference lookups, which the schema only hints at. Baseline 3 is appropriate since the schema carries most of the burden.

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 specific verb and resource ('Open an interactive form to create or edit a ServiceNow record') and enumerates concrete tables (incident, change_request, problem, any table). The 'interactive form... The user reviews and saves' framing implicitly distinguishes it from direct-write siblings like create_record or update_record, though it never names them explicitly.

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

Usage Guidelines4/5

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

It states the key selection rule clearly: 'Omit sys_id to create a new record; pass values to prefill,' which tells the agent how to switch between create and edit modes. It lacks an explicit contrast against non-interactive write tools, so the agent must infer that this path is for human-in-the-loop review rather than automated mutation.

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