Skip to main content
Glama

set_language

Restart the app under test in a specified language to verify translations or capture localized screenshots while leaving the device and other apps unchanged.

Instructions

Restart the app under test in another language — a language tag such as de, fr, ja or pt-BR, or 'default' for the device's language — e.g. to check translations or take localized screenshots. Only the app changes; the device, its status bar and other apps keep their language. iPhone, iPad, Apple TV and Android 13+; not Roku or embed sessions.

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": {
      "language": "<language>"
    },
    "name": "set_language"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesA language tag (de, fr, ja, pt-BR, zh-Hans, …) or 'default' for the device's own language.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With only readOnlyHint=false supplied, the description carries most of the burden and does so well: it discloses the side effect (the app is restarted, not merely configured), the blast radius (device, status bar, and other apps untouched), and platform limits. It stops short of stating whether the app's in-progress state or data is lost by the restart, which matters for a non-read-only operation.

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?

Front-loads the action, then scope, then examples, then platform constraints in a single dense passage with no filler. Every clause (app-only, platform list, exclusions) carries decision-relevant information.

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 two-parameter mutation with no output schema, the description covers purpose, target, scope, and platform support, while the schema handles session targeting and fallbacks. The one gap is post-restart state handling, which an agent running a stateful test would want to know.

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?

Schema coverage is 100% and the schema already defines both parameters including the 'default' fallback and tag examples. The description's inline examples (de, fr, ja, pt-BR, 'default') largely restate that, so it adds little meaning beyond the structured field; baseline 3 applies.

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?

Opens with a specific verb+resource ('Restart the app under test in another language') and immediately narrows scope: only the app changes, not the device or other apps. That contrast with set_status_bar and other device-wide setters makes it distinguishable from siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ('to check translations or take localized screenshots') and explicit exclusions ('not Roku or embed sessions'), plus a platform matrix (iPhone, iPad, Apple TV, Android 13+). An agent knows both when to reach for it and when it will fail.

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