Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Lookup Application or Plugin

lookup_app

Search for ServiceNow applications and platform plugins by name, scope namespace, or plugin ID. Returns sys_id, name, scope, version, active status, and type for each match.

Instructions

Search for ServiceNow applications (scoped apps) and platform plugins by name, scope namespace, or plugin ID. Returns sys_id, name, scope, version, active status, and type for each match.

ServiceNow uses a hierarchical table structure for packages:

  • sys_scope: All scoped applications (base table)

    • sys_app: Custom applications in development on this instance

    • sys_store_app: Applications installed from the ServiceNow Store or company app repo

  • sys_plugins: Platform plugins

Key use cases:

  • Find an application's sys_id to pass as the scope parameter to execute_script (to run scripts within that application's scope)

  • Check whether a specific app or plugin is installed/active on the instance

  • Look up version, scope namespace, and vendor info for any application or plugin

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.
search_termYesName, scope namespace (e.g., "x_acme_my_app", "sn_vul"), or plugin ID (e.g., "com.snc.vulnerability_response") to search for. Case-insensitive partial matching (contains).
typeNoFilter search scope. "app" searches scoped applications only (sys_scope table which includes both custom apps and store apps), "plugin" searches platform plugins only (sys_plugins table), "all" searches both. Default is "all".all
active_onlyNoWhen true, only returns active/installed applications and plugins. Default is false (returns all matches regardless of active status).
Behavior3/5

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

No annotations are provided, so the description must disclose all behavioral traits. It describes the search and filtering behavior but does not explicitly state that the tool is read-only (no side effects). It lacks mention of rate limits, auth requirements, or error handling.

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

Conciseness3/5

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

The description includes multiple paragraphs with detailed context and examples. While useful, it is longer than necessary; the first sentence already conveys the core purpose. Some content could be trimmed without losing essential information.

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

Completeness5/5

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

Given the complexity of searching across multiple tables (sys_scope, sys_app, sys_store_app, sys_plugins), the description is comprehensive. It explains the structure, filters, and provides concrete use cases, making it complete for an agent to use effectively.

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

Parameters4/5

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

Schema coverage is 100%, so the description is not required to add param details, but it provides valuable context such as the hierarchical table structure and how search_term can be a name, scope, or plugin ID. This enhances understanding beyond the schema alone.

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?

The description clearly states the tool's purpose: 'Search for ServiceNow applications (scoped apps) and platform plugins by name, scope namespace, or plugin ID.' It specifies the verb (search), resource (applications/plugins), and what is returned, distinguishing it from siblings like list_scoped_apps and get_app_details.

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

Usage Guidelines4/5

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

The description provides explicit key use cases, such as finding a sys_id for execute_script or checking installation status. It explains the hierarchical table structure but does not explicitly state when not to use this tool versus listing tools, leaving some inference needed.

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