Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

White-label setup status

get_platform_setup
Read-onlyIdempotent

Shows what is already set on this swift_platform account and what is left: email, app, name, colours, hostnames, shared app id, support, icon, mark, modules, tabs, and a way to pay. tabs is the current list for each platform. optional.mark_dark is the dark-background mark. It is not required, and a missing one is not listed in remaining. A saved card is required only when the account has no credit. Unlimited credit or a positive wallet balance satisfies that check. module_groups lists the catalogue by the section stored on each row. A group is not a separate price and not a separate setup step. It does not describe the people who use the app.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond that: optional.mark_dark is not required and is not listed in remaining, and a saved card is required only when the account has no credit and no positive wallet balance.

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?

The description is front-loaded with the core purpose and then explains specific fields and conditions. It is somewhat long, but each sentence clarifies setup status semantics rather than repeating the title or annotations.

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?

With no output schema, the description carries the burden of explaining returned information, and it does so by naming the setup areas and clarifying tabs, optional.mark_dark, saved-card requirements, and module_groups. It is not an exhaustive field-by-field return contract, but it is sufficient for an agent to understand the status payload.

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?

There are zero input parameters, so the schema baseline is 4. The description does not need to explain parameter syntax, and its discussion of optional.mark_dark and module_groups concerns returned data rather than inputs.

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 description states a specific read operation: it shows what is already set and what is left on a swift_platform account, then enumerates the setup areas. This clearly distinguishes it from the setter siblings such as set_platform_app_settings and set_platform_modules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied as a status check, and the description includes one exclusion: it does not describe the people who use the app. However, it does not explicitly say when to use this instead of related getters or before calling the setter tools.

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