Skip to main content
Glama

owa_language

List installed and catalog languages, check a language's state, and install missing or re-enable turned-off languages for the Open Worship App.

Instructions

The app languages. list: the installed ones and the catalog's others. check the language some words name (English name, own name, code or locale): state english, installed, turned-off, missing (with size in bytes), unavailable or unknown. install downloads a missing one from the catalog, or turns a turned-off one on; it does not switch the app to it.

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": {
      "action": "<action>"
    },
    "name": "owa_language"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: install is disclosed as a network/catalog download that can also re-enable a turned-off language, and its side-effect boundary (does not switch the app) is made explicit. The check action's possible outcomes are enumerated (english, installed, turned-off, missing with size in bytes, unavailable, unknown), which tells the agent what to expect back. It omits failure/permission behavior and pagination of the catalog list.

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?

Dense, front-loaded, and each clause maps to one action, so nothing is wasted. The phrasing is telegraphic in places ('`check` the `language` some words name'), which costs a little readability but not correctness.

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 tool with no output schema and no annotations, the description covers action semantics, accepted input formats, and the return states of check. Gaps are minor: whether `language` is required for check/install and what happens on an invalid identifier are left unstated.

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?

Schema coverage is 0%, so the description must compensate, and it does: `language` is documented as accepting an English name, own name, code, or locale, and each `action` enum value is given meaning along with its inputs and outcome. Both parameters gain semantics that the bare schema does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (app languages) and enumerates the three concrete operations with their effects: list installed plus catalog entries, check a language's state, install/turn-on. That is a specific verb+resource statement an agent can act on. It stops short of a 5 because it never contrasts itself with a sibling such as owa_app_state.

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 by the action breakdown: list to enumerate, check to inspect one language's state, install to obtain or enable one. The most useful exclusion is stated explicitly ('it does not switch the app to it'), which prevents a likely misuse. However, there is no stated when-not or pointer to any alternative tool for actually changing the app's display language.

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