AI MCP ServiceNow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-weatherC | Tool to get the weather of a city |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly distinct by default.
Since there is only one tool, naming consistency is inherently perfect—there are no other tool names to be inconsistent with. The tool name 'get-weather' follows a clear verb-noun pattern.
A single tool is too few for a server named 'AI MCP ServiceNow', which suggests a broader scope related to ServiceNow operations, not just weather. This extreme mismatch indicates the tool set is severely under-scoped for the apparent purpose.
The tool set is severely incomplete for the inferred domain of ServiceNow, as it only provides a weather tool with no coverage of typical ServiceNow operations like incident management, user queries, or data retrieval. This leaves obvious and significant gaps that will cause agent failures.