Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Query ServiceNow Table

query_table

Query ServiceNow tables using encoded queries, field selection, and display values. Retrieve records from any table like incident or user.

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
instanceNoThe ServiceNow instance auth alias (e.g., "myinstance", "prod"). If not provided, falls back to the SN_AUTH_ALIAS environment variable.
tableYesThe ServiceNow table name to query (e.g., "incident", "sys_user", "cmdb_ci_server"). This is the internal table name, not the label.
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.
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.
limitNoMaximum number of records to return. Default is 20, max is 1000.
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.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions supports for encoded queries, field selection, and display values, but does not explicitly state that the tool is read-only, safe, or any side effects. It does not contradict annotations since none exist.

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?

The description is two sentences plus a usage line, all essential and front-loaded. No redundant information, and the structure efficiently separates purpose from details.

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?

Given no output schema, the description does not explain the return format beyond 'records'. It covers filtering and field selection, but lacks details on error handling, pagination, or ordering. Adequate but with gaps for a comprehensive query 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%, with each parameter having a clear description. The description provides examples of query strings and field selection, adding context beyond the schema. However, since schema already covers parameters thoroughly, the added value is moderate.

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 clearly states 'Query any ServiceNow table using the Table API' with a specific verb and resource. It mentions returning records matching criteria, which defines the core purpose. However, it does not explicitly differentiate from sibling tools like 'count_records' or 'lookup_table', lacking explicit differentiation.

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 description says 'Use this for general-purpose data retrieval from any table', which implies context but does not provide explicit when-to-use or when-not-to-use guidance. No alternatives are suggested, and restrictions like read-only or rate limits are omitted.

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