Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_table_get

Read-only

Retrieves a single ServiceNow table record by sys_id, letting you fetch specific columns or all fields and choose display or stored values.

Instructions

Read one record from a ServiceNow table by its sys_id.

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

Input Schema

NameRequiredDescriptionDefault
tableYesTable name, lowercase letters, digits and underscores only. Example: incident.
fieldsNoComma separated list of columns to return. Example: number,short_description,state. Leave out to get every column.
sys_idYesThe sys_id of the record: 32 hex characters.
display_valueNofalse returns stored values (the default), true returns display values such as names for references, all returns both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description contributes nothing beyond that — no mention of behavior when the sys_id is not found, permission requirements, or what the response looks like. For a simple read the annotation covers most of the safety profile, but the description adds essentially no behavioral context.

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 front-loaded sentence with zero redundant wording. It states the essential constraint (one record, by sys_id) immediately.

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 read-only fetch with fully documented parameters and a readOnlyHint annotation, the definition is adequate; the only real omission is not hinting at the not-found error case or the shape of the returned record, which matters slightly since there is no output schema.

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%, with each parameter documented including the display_value enum and the fields projection, so the schema carries the semantic load. The description mentions only sys_id and adds no format or usage nuance 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 (read) and resource (one record from a ServiceNow table) and pins the lookup key to sys_id. The single-record framing implicitly separates it from the list-style sn_table_query, though no sibling is named 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?

Usage is only implied: an agent can infer this is the tool for fetching a known record when the sys_id is already in hand. There is no explicit statement of when to prefer this over sn_table_query or what to do when the sys_id is unknown.

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