Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Create the white-label app

create_platform_app
Idempotent

Creates the Android, iOS, web, and kosher shells for this swift_platform account. The connected account must be the app owner, not a person who uses the app. Omitted confirm returns a preview. idempotency_key is required when confirm is true. An app id already used by another company is refused. Nothing is charged.

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": {
      "app_name": "<app_name>"
    },
    "name": "create_platform_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoOmitted returns a preview on every client. True creates the app.
app_nameYes
idempotency_keyNoRepeats the same result instead of charging again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

The annotations only declare the generic write/idempotent/non-destructive profile; the description adds substantive behavior: the default is a non-mutating preview, idempotency_key becomes mandatory once confirm is true, a duplicate app id owned by another company is rejected, and no charge occurs. These are exactly the operational traits an agent needs before firing a write.

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?

Five short sentences, front-loaded with the core action, and each adds a distinct fact (prerequisite, preview default, conditional key, rejection rule, cost). The 'swift_platform' and 'kosher shells' jargon slightly slows parsing, but there is no filler.

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 3-parameter mutation with no output schema, the description covers ownership requirements, the preview path, idempotency requirements, conflict behavior, and cost. It stops short of saying what a preview actually returns or what identity/permission the caller must present beyond being the owner, but the essentials are present.

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 67% and app_name has no schema description at all; the description compensates for confirm (preview vs create) and idempotency_key (conditionally required, de-duplicates rather than re-charging), which the schema alone would not make clear. It never explains app_name — its format, or whether 'app id' in the description is the same as app_name — leaving one real gap.

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?

States a specific verb and resource ('Creates the Android, iOS, web, and kosher shells') and scopes it to 'this swift_platform account', which cleanly separates it from set_platform_app_settings and the generic create_* siblings. An agent can tell it provisions an app rather than configuring one.

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?

Gives a clear selection rule between a preview and a real creation ('Omitted confirm returns a preview') and a prerequisite ('The connected account must be the app owner, not a person who uses the app'). It does not explicitly name a sibling for the not-this case, but the preview/confirm fork is the main decision and it is stated.

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