Skip to main content
Glama
ausper-tech

servicenow-mcp

by ausper-tech

Query a ServiceNow table

servicenow_query_table
Read-onlyIdempotent

Query and read records from any ServiceNow table using encoded queries. Retrieve incidents, changes, users, or CMDB items with field selection and pagination.

Instructions

Read records from any ServiceNow table using an encoded query. This is the main tool for answering questions about incidents, changes, users, CIs or anything else stored on the instance. Read-only. Results are capped by the server's policy and every cap applied is reported in the result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum records to return. Clamped to the server's configured ceiling, and the clamp is reported.
queryNoA ServiceNow encoded query. This is NOT SQL: conditions are joined by '^' for AND and '^OR' for OR, with no spaces around operators, and there is no WHERE or SELECT. Example: 'active=true^priority=1^ORDERBYDESCsys_created_on'. Call servicenow_query_syntax for the full operator list. Omit to match every record. A query that names a field which does not exist returns zero records rather than an error, so verify field names with servicenow_describe_table when a result is unexpectedly empty.
tableYesSystem name of the table, not its UI label: 'sys_user' rather than 'User', 'incident' rather than 'Incidents'. Use servicenow_list_tables to find it.
fieldsNoColumns to return. Naming the few you need is markedly cheaper than the default of every column, and keeps results readable. Omit for all columns.
offsetNoRecords to skip; use with 'limit' to page.
display_valueNo'true' (the default here) resolves references to human-readable names, so assigned_to reads 'Alice Smith'. 'false' returns raw sys_ids, which you want when feeding a value into another query. 'all' returns both.
include_totalNoAlso report how many records match in total, at the cost of one extra request. Worth it whenever you need to know if you are seeing everything.
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds that results are capped by server policy, with cap reported, and that non-existent fields return zero records. This goes beyond annotations.

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?

Four concise sentences with no fluff. Each sentence adds distinct value: purpose, primary use case, read-only nature, and result capping behavior.

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 complexity (7 params, no output schema), the description covers core behavior and usage context. Lacks details on return format, but that is acceptable as it is a query tool with standard pagination.

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?

Input schema has 100% coverage with detailed descriptions. The description provides additional usage context (e.g., query format examples) but does not add meaning beyond the schema's parameter descriptions.

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?

Clearly states 'Read records from any ServiceNow table using an encoded query.' It is the main querying tool, distinguishing from siblings like get_record (single record) and count_records (count).

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?

Identifies as the main tool for answering questions about instances, and includes read-only notice. Does not explicitly list when to use alternatives, but sibling names imply usage boundaries.

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/ausper-tech/servicenow-mcp'

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