Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Set white-label app tabs

set_platform_tabs
DestructiveIdempotent

Sets the tab list for this swift_platform app: keys, labels, order, the default tab, and the centre tab. platform is web, ios, android, or all. Omitted platform updates every platform, including the kosher profile when this app has one. Omitted confirm returns a preview and does not save. A tab or view whose module is off is left out. conversations, feed, pa, and me are tab keys. A key the apps do not support is refused and the current tabs stay as they are. This does not charge.

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": {
      "tabs": "<tabs>"
    },
    "name": "set_platform_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabsYesTabs in order. Each item is key, label, and optional views.
centerNoSame as centre.
centreNoTab key shown in the centre. center is the same field.
confirmNoOmitted returns a preview on every client. True saves.
defaultNoTab key that opens first.
group_idNoApp id from create_platform_app. Omit when there is one app.
platformNoWhich app shell. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint, and readOnlyHint=false, and the description adds genuine context beyond them: preview-without-confirm semantics, that module-disabled tabs are dropped, that unsupported keys cause rejection with the existing tabs preserved, and that the operation does not charge. It stops short of explicitly saying the existing tab list is replaced wholesale, which is the main destructive behavior an agent should know.

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?

Front-loaded with the core action, then terse sentences each carrying a distinct constraint (platform scoping, confirm preview, module gating, valid keys, failure mode, no charge). Dense but no filler; slightly list-like flow rather than grouped by parameter versus behavior.

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

Completeness4/5

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

For a 7-parameter mutation with no output schema, the description covers the risky paths: preview mode, module-based omission, and rejection behavior. What remains implicit is the replacement semantics of the tabs array and what the preview response looks like, but overall it is sufficient to call the tool safely.

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 baseline is 3; the description earns extra credit by clarifying that an omitted platform updates every shell including the kosher profile, and that omitting confirm produces a preview rather than a save. It also names concrete tab keys (conversations, feed, pa, me), which the schema does not.

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 first sentence gives a specific verb and resource ('Sets the tab list for this swift_platform app') and enumerates exactly what is being set: keys, labels, order, default tab, and centre tab. That distinguishes it from neighbours like set_platform_app_settings or set_platform_modules without needing the schema.

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?

It explains the key usage decision points: omit confirm for a preview, omit platform to target every platform, and the call is refused for unsupported keys rather than silently applied. It does not name sibling tools or state when to prefer a different tool for settings outside the tab list, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Widely toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources