Skip to main content
Glama
ausper-tech

servicenow-mcp

by ausper-tech

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
servicenow_query_tableA

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.

servicenow_get_recordA

Fetch a single record by its 32-character sys_id. Use this after a query has given you an id, or when the user supplies one. Returns a clear 'no such record' message rather than an error if nothing matches.

servicenow_count_recordsA

Count records matching a query without transferring any of them. One request, a few bytes, and no context cost regardless of the number. Prefer this over querying with a large limit whenever the question is 'how many'.

servicenow_describe_tableA

List a table's columns with their types, labels and reference targets, including columns inherited from parent tables - most of an incident's fields are declared on 'task', and a listing that omitted them would be misleading. Call this before writing a query against an unfamiliar table, or when a query returns unexpectedly little.

servicenow_list_tablesA

Search the instance's tables by system name or label. Use it to turn a user's words - 'the change requests', 'our CMDB servers' - into the system name the other tools need. Tables blocked by this server's policy are omitted, and the count of omissions reported.

servicenow_query_syntaxA

The full ServiceNow encoded-query operator reference, with worked examples. Makes no network call. Read this before guessing at query syntax - encoded queries look enough like SQL to invite the wrong habits, and a malformed query returns an empty result set rather than an error, which is easy to misread as 'no matches'.

servicenow_check_connectionA

Verify that credentials work, report which account the server authenticates as, and show the limits currently in force. Start here when another tool fails with a permission error, to tell 'wrong credentials' apart from 'right credentials, missing role'.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a distinct purpose: querying, single record retrieval, counting, schema inspection, table discovery, syntax reference, and connection validation. Descriptions clearly differentiate them and include usage guidance, leaving no ambiguity.

Naming Consistency5/5

All tools follow the same pattern: 'servicenow_' + verb_noun (e.g., query_table, get_record, count_records). The convention is uniform and predictable, aiding intuitive selection.

Tool Count5/5

7 tools is appropriate for a read-only ServiceNow integration. Each tool covers a necessary operation without redundancy, and the count is neither too sparse nor overwhelming.

Completeness5/5

For its stated read-only purpose, the tool set is complete: querying, retrieving, counting, schema exploration, table discovery, syntax reference, and connection check. No obvious gaps for the intended use case.

Maintenance

ActivityStale
ResponsivenessNo issues