Skip to main content
Glama
Sign In
servicenow-api

servicenow-api

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Deploy

servicenow_sdk_deploy

Install or update an app on a target ServiceNow instance, syncing local SDK code with the remote environment.

Instructions

Install/update the app on the target instance (now-sdk install, alias deploy).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "servicenow_sdk_deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
params_jsonNo{}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the specific action ('install/update') and the CLI command, but does not disclose further behavior such as whether it overwrites an existing app, required authentication, or reversibility.

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?

A single, front-loaded sentence with no wasted words. It efficiently conveys the core action and the CLI alias.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema and zero parameter documentation, the description is too sparse. It lacks critical context such as how the target instance is specified, what credentials are needed, and what happens on failure, leaving substantial gaps for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters (params and params_json). The description does not explain what these parameters represent or provide any syntax, examples, or constraints, leaving the agent with no guidance beyond the generic schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('install/update') and resource ('the app on the target instance'), and provides the CLI command alias. This distinguishes it from most siblings, though it does not explicitly differentiate from tools like servicenow_app_repo_install or servicenow_batch_install.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives. The description does not mention prerequisites, target instance selection, or how it relates to sibling install/deploy tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools