Skip to main content
Glama

create_mobile_layout

Create a mobile layout for a specific ServiceNow view by defining its name, target table, layout type, and optional card template.

Instructions

Create a mobile layout for a specific view. [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>",
      "table": "<table>"
    },
    "name": "create_mobile_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesLayout name
typeNoLayout type: list, form, detail (informational; cards are used by all of them)
tableYesTarget table
templateNoCard template (sys_sg_view_template sys_id or name; default: the first active template)
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv5.0.1
    • addedInput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / template
      Added value: +{
      +  "description": "Card template (sys_sg_view_template sys_id or name; default: the first active template)",
      +  "type": "string"
      +}
    • changedInput schema / properties / type / description
      Previous value: -"Layout type: list, form, detail"New value: +"Layout type: list, form, detail (informational; cards are used by all of them)"
  2. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the "**[Write]**" tag merely restates that this is a write. The description adds nothing beyond the annotations: no note that idempotentHint=false means repeated calls create duplicates, no permission/auth requirements, no side effects such as template defaults being applied.

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?

Extremely short and front-loaded: purpose first, mutation marker second, zero filler. The only detraction is that the brevity leaves the "specific view" phrase unexplained and the write tag is redundant.

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 5-parameter creation tool with no output schema, the description omits anything beyond the bare action – no mention of what a layout belongs to, what happens on name collision, or what is returned. Annotations cover safety but not the creation contract.

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 80%, so the schema itself carries most parameter meaning, including the type enum hints and the template default. The description contributes no additional semantics (e.g. name uniqueness, whether template applies retroactively), so the baseline 3 applies.

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?

States a specific verb and resource ("Create a mobile layout") plus a scoping qualifier ("for a specific view"), which distinguishes it from list_mobile_layouts and the other create_mobile_* siblings. Minor confusion: "view" is not an actual parameter (the schema offers type: list/form/detail), so the scoping phrase does not map cleanly onto the input contract.

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 this versus list_mobile_layouts, create_mobile_applet, or create_mobile_app_config, and no prerequisites (e.g. must a mobile app config or target table already exist?). The agent is left to infer everything about selection context.

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