Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_table_query

Read-only

Query ServiceNow table records using encoded filters, field selection, sorting, and limit/offset paging to retrieve matching records and totals.

Instructions

Read records from a ServiceNow table with the Table API. Returns count (records in this reply), total (all matching records, when the instance reports it) and records. Use limit and offset to page through large results.

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": "sn_table_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many records to return. Default 20, at most 200.
queryNoServiceNow encoded query. Example: active=true^priority=1. Leave out to match every record.
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.
offsetNoHow many records to skip, for paging. Default 0.
order_byNoColumn to sort by, oldest or smallest first. Put DESC in front for the reverse order. Example: DESCsys_created_on.
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

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds genuinely new behavior: the response keys (count, total, records) and the caveat that total appears only 'when the instance reports it'. It does not mention ACL-based record filtering, which would matter for a ServiceNow reader, but it is well above the annotation bar.

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?

Three short sentences, front-loaded with what the tool does, then return shape, then paging advice. No redundancy or filler; each sentence carries distinct information.

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?

With no output schema, the description usefully explains the three return keys and the conditional nature of total. The paging story is covered; missing pieces are permission/ACL effects and error behavior, which are secondary for a read-only tool.

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 every parameter including paging, encoded query syntax, field lists, ordering and display_value is already documented in the schema. The description only echoes the limit/offset paging relationship, adding little meaning beyond it.

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 — 'Read records from a ServiceNow table' — and names the underlying API (Table API). It is clearly distinguishable from write siblings like sn_table_create/delete/update, though it never explicitly separates itself from the look-alike sn_table_get or sn_table_schema.

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 usage direction is 'Use limit and offset to page through large results', which is practical but narrow. There is no guidance on when to prefer this list-style read over sn_table_get or sn_table_schema, and no mention of required permissions or instance caveats.

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