Skip to main content
Glama
jshsakura

mfa-servicenow-mcp

by jshsakura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

download_app_sources

Export the full source of a ServiceNow app scope to disk, including all groups and dependencies. Requires the scope name or namespace.

Instructions

FULL/all source of an app scope to disk (all groups+deps). scope REQUIRED — ask user. Step 1, not portal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeYesREQUIRED app namespace (x_...) or app name. Ask the user if not given.
resumeNoSkip stages a prior timed-out call finished. false = download everything again.
page_sizeNo
backgroundNoRun in background; call again (same args) to poll progress, then result.
output_dirNoOmit — default path is canonical and reused. Set only for one-off export.
build_graphNoAlso run the offline audit (relationship graphs) after download. No API cost.
incrementalNoRe-download only records changed since last sync (sys_updated_on).
only_activeNo
include_schemaNo
acl_script_onlyNo
auto_resolve_depsNoAfter download, fetch missing cross-scope SI/widget/provider/ui_macro deps.
reconcile_deletionsNoWarn about local records deleted on the instance. No auto-delete.
max_records_per_typeNo
include_widget_sourcesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.24.61
    • changedInput schema / properties / resume / description
      Previous value: -"Replay finished stages from a prior timed-out call; skip re-downloading them."New value: +"Skip stages a prior timed-out call finished. false = download everything again."
  2. First observedv1.18.41

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It only says source is downloaded to disk; it does not mention long-running/background behavior, where files are written, how resume interacts with prior runs, or whether any instance state is modified.

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?

The description is very short and front-loaded with the essential action. Minor redundancy in 'FULL/all' and the cryptic 'not portal' phrase are the only detractions.

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 tool with 14 parameters, no annotations, and no output schema, this description is far too thin. It does not explain invocation flow, background polling, output location, or parameter interactions, so an agent would struggle to call it correctly beyond providing the required scope.

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

Parameters2/5

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

Schema description coverage is only 57%, so the description should compensate for undocumented parameters. It only repeats that scope is required, which the schema already states, and provides no help for the six undocumented parameters.

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 action ('download ... source of an app scope to disk') and defines the scope granularity ('all groups+deps'). It stops short of a 5 because 'not portal' only hints at differentiation from download_portal_sources without explicitly naming the alternative scope.

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?

'Step 1' gives weak workflow context, but the description never states when to choose this tool over alternatives or when not to use it. 'not portal' is a vague exclusion rather than actionable guidance.

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