agent4.io

set_pwa_branding

Configure a specific agent's PWA branding and install experience (applies to that agent's /s/ standalone chat pages — what gets installed to the home screen is one agent's entry page, so each agent is its own app).

- `agent`: the agent name whose install branding to configure (required).
- `icon_source_url`: public URL of one master image (PNG/JPG/WebP ≥192×192, ideally a square
  logo). The server derives the full set: browser-tab favicon(48) + install icons 192/512 +
  Android maskable(512). Non-square images are centre-cropped. Once set, "Add to Home Screen"
  installs this agent's own icon.
- `install_prompt`: prompt style — `banner` (a dismissible slim bar inside the chat page,
  default), `card` (a card shown on first visit; more visible, more intrusive), `off` (no
  prompt). Android/Chrome uses the system install dialog; iOS automatically switches to a
  "Share → Add to Home Screen" illustrated guide.

Icon/prompt params optional, settable independently. Returns the final config (icon URLs +
install_prompt). Full walkthrough in the Cookbook's configure-branding.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent`	Yes
`install_prompt`	No
`icon_source_url`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description fully carries the behavioral burden and goes deep: it explains server-side derivation of favicon/icons/maskable sizes, centre-cropping of non-square images, platform-specific install prompt behavior (Android system dialog vs iOS Share guide), and the return value (final config). These traits are not inferable from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description opens with a concise summary, then uses a bulleted list for parameter semantics, and wraps up with a clear statement about optionality and return. Every sentence adds value and there is no wasted space; the structure makes complex platform details scannable.

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

Completeness5/5

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

Given that the tool has 3 parameters, an output schema, and no annotations, the description covers all essential aspects: purpose, parameter meaning, behavioral variations (platform differences), and return value. It even points to a Cookbook walkthrough for further detail, making the description self-sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides only titles and defaults with zero descriptions (0% coverage), so the description completely compensates. It defines each parameter in detail: `agent` (required target), `icon_source_url` (format, minimum size, squareness, cropping, derived sizes), and `install_prompt` (all three options with behavioral implications).

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 action ('Configure a specific agent's PWA branding and install experience') and clearly distinguishes it from siblings by explaining the per-agent standalone chat page scope. It also names the exact resource (agent branding) and the unique effect (each agent is its own app), making the purpose unmistakable.

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?

The description provides strong context for when to use this tool (when configuring an agent's PWA branding/install experience) and notes that icon/prompt parameters are optional and independent. However, it does not explicitly exclude alternatives or name when not to use it, though no sibling tool competes with this function.

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

All agent4.io tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Tools are mostly distinct by domain and action. A few pairs like add_knowledge_file vs add_knowledge_text or build_knowledge_index vs patch_knowledge_index could cause confusion, but descriptions clearly differentiate them.

Naming Consistency4/5

The vast majority follow a consistent verb_noun snake_case pattern (create_*, list_*, get_*, update_*). A few outliers like tenant_info, usage_stats, and page_context_stats are noun-first, deviating slightly from the otherwise uniform scheme.

Tool Count1/5

With 50 tools, this is a very large surface that exceeds typical well-scoped server sizes. Even for a broad platform management API, the sheer number makes it heavy and potentially overwhelming, matching the '50+' extreme mismatch category.

Completeness2/5

The server covers creation, reading, updating, and listing for most resources but lacks any delete operations (no delete_agent, delete_knowledge_base, delete_skill, delete_share, delete_storyline, delete_page_context). This is a significant gap in lifecycle coverage that will force agents to work around missing functionality.

Resources

Need Help?