best-practices-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SN_INSTANCE_URL | No | ServiceNow instance URL. Defaults to https://mynow.servicenow.com. | https://mynow.servicenow.com |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| servicenow_searchA | Search ServiceNow's public best-practices library (mynow.servicenow.com) across Knowledge, Best Practices, Developer Portal docs, and other indexed content. No authentication required. Leave contentType unset to search all sources; use the 'table' field on prior results to discover valid contentType filter values. A natural-language content-type cue in the query itself (e.g. 'stream connect best practices') is detected and routed to that contentType filter automatically, with the cue phrase removed from the search text — see the response's searchedQuery/detectedContentType fields for what was actually searched. Set contentType explicitly to override this detection. contentType filtering only applies to a small fixed raw page, not the full corpus — if that filter would return nothing despite real matches existing (totalResults > 0), the response falls back to unfiltered results and sets contentTypeFilterDegraded/note rather than silently returning empty. |
| servicenow_list_content_typesA | List content-type values for servicenow_search's contentType filter: raw internal table identifiers (e.g. 'u_hi_kb_knowledge_gsdr') paired with their human-readable label. These cannot be guessed from standard ServiceNow table names (e.g. 'kb_knowledge' is wrong) — a wrong guess silently returns zero results instead of erroring. Backed by a cache built from real search traffic plus a warm-up sweep on first use or once the cache is more than 6 hours old; set refresh to force a fresh sweep. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists content types for filtering, the other performs searches across the knowledge base. No ambiguity between them.
Both tools follow the consistent pattern 'servicenow_verb_noun' (list_content_types and search), making them easily distinguishable and predictable.
With only 2 tools, the server is minimal but appropriate for its narrow focus on searching ServiceNow best practices. The helper tool is essential for effective use of the search tool.
The tool surface covers the core workflows: retrieving valid content types and performing searches with smart fallback. Minor gaps exist (e.g., no tool to fetch a single result in detail), but overall it's well-scoped.