Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

by sonisoft-cnanda
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Pull Script from ServiceNow

pull_script

Retrieve a script from a ServiceNow instance and save it to a local file. Supports Script Includes, Business Rules, UI Scripts, UI Actions, and Client Scripts.

Instructions

Pull a script (Script Include, Business Rule, UI Script, UI Action, Client Script) from a ServiceNow instance and save it to a local file. The script content is read from the appropriate table and written to the specified file path.

Supported script types:

  • sys_script_include (Script Include)

  • sys_script (Business Rule)

  • sys_ui_script (UI Script)

  • sys_ui_action (UI Action)

  • sys_script_client (Client Script)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe ServiceNow instance auth alias (e.g., "myinstance", "prod"). If not provided, falls back to the SN_AUTH_ALIAS environment variable.
script_nameYesThe name of the script record on the instance (e.g., "MyScriptInclude").
script_typeYesThe type of script to pull.
file_pathYesLocal file path to write the script content to.

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

Describes basic behavior (reading from table, writing to file) but lacks disclosure of side effects (non-destructive), auth requirements, or failure behavior. No annotations to offset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise two-paragraph structure. First paragraph states action clearly; second paragraph lists types (some redundancy with schema). No unnecessary fluff.

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

Completeness3/5

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

Describes tool purpose and parameters but omits return value or success/failure indicators. No output schema. Adequate but not fully complete for a file-writing tool.

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

Parameters3/5

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

Schema covers 100% of parameters with descriptions. Description adds minimal value beyond listing script types (already in enum). Baseline score applies.

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

Purpose5/5

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

Description clearly states it pulls a script from ServiceNow and saves to local file, listing supported script types. Distinguishes from siblings like push_script.

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 on when to use vs alternatives (e.g., push_script, execute_script). No mention of prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sonisoft-cnanda/now-sdk-ext-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server