Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Query ServiceNow Table

query_table
Read-only

Query any ServiceNow table to retrieve records matching specified criteria. Supports encoded query strings, field selection, and display value resolution for general-purpose data retrieval.

Instructions

Query any ServiceNow table using the Table API. Returns records matching the specified criteria. Supports encoded query strings, field selection, and display value resolution.

Use this for general-purpose data retrieval from any table (incident, sys_user, cmdb_ci, change_request, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records to return. Default is 20, max is 1000.
queryNoA ServiceNow encoded query string to filter records. Examples: "active=true^priority=1", "short_descriptionLIKEnetwork^state!=7", "sys_created_on>javascript:gs.daysAgoStart(7)". If omitted, returns all records up to the limit.
tableYesThe ServiceNow table name to query (e.g., "incident", "sys_user", "cmdb_ci_server"). This is the internal table name, not the label.
fieldsNoComma-separated list of field names to return (e.g., "sys_id,number,short_description,state"). If omitted, all fields are returned. Specifying fields improves performance and readability.
instanceNoThe ServiceNow instance auth alias (e.g., "myinstance", "prod"). If not provided, falls back to the SN_AUTH_ALIAS environment variable.
display_valueNoWhen true, returns display values instead of internal values for reference and choice fields. For example, assignment_group returns the group name instead of the sys_id.
Behavior4/5

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

With annotations already indicating read-only and open-world behavior, the description adds valuable context by mentioning support for encoded query strings, field selection, and display value resolution. It does not contradict the annotations and gives a sense of the tool's capabilities beyond the structured metadata.

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?

The description is concise and well-structured, with a clear opening sentence stating purpose, followed by a brief capability summary and a usage note. Every sentence earns its place with no redundant 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?

Given the moderate complexity (6 parameters, no output schema), the description covers the main purpose, general applicability, and key features. It does not describe the return format or pagination details, but the schema and openWorldHint annotation reduce the burden on the description to cover those aspects.

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?

The input schema already has 100% coverage with detailed descriptions for all parameters, so the baseline is 3. The description mentions key features (encoded queries, field selection, display values) but does not add new parameter-level semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool queries any ServiceNow table via the Table API, using a specific verb and resource. It also distinguishes itself as general-purpose data retrieval, which separates it from sibling tools that target specific tables or operations.

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?

The description provides clear usage context by stating 'Use this for general-purpose data retrieval from any table,' which tells the agent when to choose this tool. However, it does not explicitly mention when not to use it or compare it with alternative sibling tools like lookup_table or query_syslog.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sonisoft-cnanda/now-sdk-ext-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server