Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

List Company Applications

list_company_apps

List company-internal applications and retrieve metadata such as name, scope, version, install status, and update availability. Apply filters by scope, sys_id, or install status.

Instructions

List company-internal applications shared within your organization. Returns application metadata including name, scope, version, install status, and update availability.

Optionally filter by scope, sys_id, or installed status.

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.
scopeNoFilter by application scope (e.g., "x_acme_my_app"). Returns only the matching application.
sys_idNoFilter by application sys_id. Returns only the matching application.
installed_onlyNoWhen true, only returns installed applications.
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as non-destructive nature, authentication requirements, or rate limits. The read-only aspect is implied but not stated.

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?

Two efficient sentences cover purpose, return value fields, and filtering options with no redundancy. Every word adds value.

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?

Given no output schema and no annotations, the description adequately states what is returned but lacks details on pagination, error handling, or the 'instance' parameter fallback behavior. It is sufficient but not comprehensive.

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 coverage is 100% and parameters are well-documented in the schema. The description adds no new semantic value beyond what the schema provides, so 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?

The description clearly states the tool lists 'company-internal applications shared within your organization' with a specific verb and resource. It differentiates from siblings like 'list_scoped_apps' by specifying the internal scope.

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

Usage Guidelines3/5

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

The description implies usage for listing internal apps and mentions optional filters, but does not explicitly state when to use this tool over alternatives or provide exclusion criteria.

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