Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SN_TIMEOUTNoHTTP timeout in seconds (default 60).60
SN_PASSWORDNoPassword for basic auth.
SN_USERNAMENoUsername for basic auth.
SN_MAX_BATCHNoMaximum number of operations in one batch (default 100).100
SN_READ_ONLYNoSet to true to refuse every write.false
SN_STORE_PATHNoWhere the local store lives.
SN_INSTANCE_URLYesThe ServiceNow instance URL, e.g. https://yourcompany.service-now.com (required). Must be https:// (or http:// for local development).
SN_DENIED_TABLESNoComma-separated deny list of tables that may not be touched.
SN_ALLOWED_TABLESNoComma-separated allow list of tables that may be touched.
SN_OAUTH_CLIENT_IDNoOAuth2 client ID for client-credentials auth (used instead of basic auth).
SN_OAUTH_TOKEN_URLNoOAuth2 token URL for client-credentials auth.
SN_REQUIRE_CONFIRMNoSet to false to drop the confirm=true requirement for writes.true
SN_SCRIPTED_REST_URLNoPath of a Scripted REST API that executes server-side script, e.g. /api/sn_gsc/v1/execute.
SN_OAUTH_CLIENT_SECRETNoOAuth2 client secret for client-credentials auth.

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
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
sn_readB

Read ServiceNow records. action=query (list records matching an encoded query), action=get (one record by sys_id), action=count (how many match). Use this instead of a separate tool per table.

sn_writeA

Change ServiceNow records. action=create, action=update, action=delete, or action=batch (apply many operations in ONE request). Every write needs confirm=true, and every write is journalled so it can be reverted.

sn_aggregateB

Aggregate over a table. action=stats (COUNT/SUM/AVG/MIN/MAX) or action=group (grouped statistics). One call answers 'how many', 'how many per group' without pulling records.

sn_schemaA

Introspect the instance's data model. action=tables (list tables), action=fields (a table's dictionary entries), action=class (a CMDB class definition), action=references (who references a field).

sn_graphA

Work the CMDB Service Graph. action=relations (a CI's edges), action=traverse (walk outward), action=dependents (what breaks if this CI goes away), action=impact (what depends on a table, field or script), action=csdm (the Common Service Data Model domains).

sn_catalogB

Service Catalog. action=items (browse), action=categories, action=variables (an item's form fields), action=order (submit an order - needs confirm=true).

sn_filesC

Record attachments. action=list, action=download, action=upload (needs confirm=true), action=delete (needs confirm=true).

sn_codeB

Find the instance's own automation. action=search (scripts mentioning a string), action=list (artefacts of a kind), action=read (one artefact), action=where_used (every reference to a name; scope='code' searches only the scripts, scope='schema' only the dictionary, empty searches both).

sn_opsB

Instance operations. action=log (system log), action=health (version and key stats), action=jobs (scheduler queue), action=properties (system properties, secrets masked), action=stats (aggregate counts).

sn_knowledgeC

Read what the server already knows. action=note_read, action=note_search, action=note_list, action=saved_list, action=saved_run (run a saved query), action=history (what was already called), action=cache_get, action=cache_list.

sn_stateB

Write to the server's own local memory. action=note_write, action=note_delete, action=saved_save, action=cache_put. Nothing here touches the ServiceNow instance.

sn_journalB

The write journal. action=journal (list applied writes and how to revert them), action=undo (revert one - needs confirm=true, and it changes the instance).

sn_adminC

Administrative surfaces. action=update_sets, action=set_update_set (bind writes to an update set - needs confirm=true), action=script (run a server-side script - needs confirm=true), action=atf (run tests - needs confirm=true), action=users, action=groups, action=roles, action=memberships.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 13 tools

Disambiguation4/5

Tools are cleanly partitioned by domain (schema, read, write, aggregate, graph, catalog, files, code, ops, knowledge, state, journal, admin), so an agent can generally pick the right one. Minor overlap remains: sn_ops action=stats versus sn_aggregate action=stats, and sn_code action=where_used versus sn_graph action=impact, though their descriptions mostly clarify the intended scope.

Naming Consistency5/5

All tool names follow a strict sn_<domain> snake_case pattern with no mixing of conventions. The action=... parameter style is used uniformly across every multi-action tool, making the surface highly predictable.

Tool Count5/5

Thirteen tools is well-scoped for a broad platform like ServiceNow, and the multi-action design consolidates many operations into coherent domains. Each tool earns its place without bloating the surface.

Completeness5/5

The surface covers the full lifecycle: schema introspection, CRUD via sn_read/sn_write, aggregation, CMDB graph traversal, catalog ordering, attachments, code search, instance operations, local memory, write journaling/undo, and admin surfaces. No obvious dead ends for the stated ServiceNow automation purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues