Skip to main content
Glama

create_mobile_app_config

Creates a new ServiceNow mobile app configuration with a name, app type, navigation bar, and branding color, letting you define request or agent mobile apps.

Instructions

Create a new mobile app configuration. [Write]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesApp name
typeNoApp type, e.g. request (Now Mobile) or agent (Mobile Agent)
navigationNoExisting navigation bar (sys_sg_navigation) sys_id; a new one is created if omitted
descriptionNoNot stored (sys_sg_native_client has no description); kept for compatibility
branding_colorNoPrimary colour hex (set on the app navigation bar)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv5.0.1
    • changedInput schema / properties / branding_color / description
      Previous value: -"Primary colour hex"New value: +"Primary colour hex (set on the app navigation bar)"
    • addedInput schema / properties / description / description
      Added value: +"Not stored (sys_sg_native_client has no description); kept for compatibility"
    • addedInput schema / properties / navigation
      Added value: +{
      +  "description": "Existing navigation bar (sys_sg_navigation) sys_id; a new one is created if omitted",
      +  "type": "string"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "App type, e.g. request (Now Mobile) or agent (Mobile Agent)",
      +  "type": "string"
      +}
  2. First observedv1.0.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds the '[Write]' marker, which merely restates those annotations, and says nothing about permissions required, side effects such as navigation records being auto-created, or whether repeated calls duplicate configs.

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?

A single short sentence with the verb and resource front-loaded; nothing is buried or padded. The '[Write]' tag is redundant with the annotations but costs little space.

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?

With a fully documented schema and annotations covering the mutation safety profile, the description is minimally sufficient for correct invocation. It nonetheless omits what the resulting configuration contains and any operational caveats, which matters for an open-world create operation with no output schema.

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 description coverage is 100%, so all five parameters (including the required 'name' and the sys_sg_navigation sys_id behaviour) are already documented in the schema. The description adds no parameter meaning beyond that, which is the baseline expectation when the schema is self-sufficient.

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 and resource ('Create a new mobile app configuration'), so an agent knows exactly what entity is produced. It does not distinguish this tool from near-siblings such as create_mobile_applet or create_scoped_app, leaving disambiguation to the names alone.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or when not to use this tool. The only signal is the '[Write]' tag, which identifies the operation class but does not guide selection among the many create_* siblings.

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