Skip to main content
Glama

create_mobile_applet

Creates a mobile applet in a mobile app to display data from a specified table, with configurable name, icon, and query.

Instructions

Create a mobile applet in a mobile app. [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_applet"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoApplet icon (sys_sg_icon sys_id or name; default: a list icon)
nameYesApplet name
queryNoEncoded query for the data item
tableYesApplet data table (a data item is created for it)
app_configNoParent app config sys_id (screens are reached via launchers, so this is not stored)
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv5.0.1
    • changedInput schema / properties / app_config / description
      Previous value: -"Parent app config sys_id"New value: +"Parent app config sys_id (screens are reached via launchers, so this is not stored)"
    • addedInput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / icon / description
      Previous value: -"Applet icon"New value: +"Applet icon (sys_sg_icon sys_id or name; default: a list icon)"
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Encoded query for the data item",
      +  "type": "string"
      +}
    • changedInput schema / properties / table / description
      Previous value: -"Applet data table"New value: +"Applet data table (a data item is created for it)"
  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, idempotentHint=false, and destructiveHint=false, so the '[Write]' tag adds nothing beyond structured data. The description says nothing about side effects, the fact that a data item is auto-created for the table, permission requirements, or whether repeated calls duplicate applets (non-idempotent).

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?

Two short fragments with no waste and the action is front-loaded. It is lean to the point of terseness, but nothing 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 6-parameter creation tool with no output schema, the description omits what is returned (e.g., the new applet's sys_id), how app_config relates to launchers, and any prerequisite or permission context. The schema carries most of the meaning, leaving the description under-specified.

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?

With schema description coverage at 83%, the schema already documents icon, name, query, table, app_config, and description. The description adds no additional meaning, so the baseline of 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 applet in a mobile app.' An agent can tell it creates one applet rather than an app config or layout, though it does not explicitly contrast itself with siblings like create_mobile_app_config or create_mobile_layout.

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, when-not-to-use, or prerequisites. The only hint is the '[Write]' tag, which restates the annotation rather than guiding 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