Skip to main content
Glama
Sign In

globalize.now

by io.github.globalize-now
OverviewDiscussionsAdmin

Set a Workflow’s target languages

set_workflow_languages
Destructive

Replace the target languages a Workflow declares, publishing its next version with nothing else changed. Pass baseVersion, the version number the change starts from (get_workflow): refused with WORKFLOW_BASE_VERSION_STALE when another version was published since, so a concurrent edit is never overwritten. The same languages publish nothing (published: false). When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

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": {
      "workflowId": "<workflowId>",
      "targetLanguages": "<targetLanguages>",
      "baseVersion": "<baseVersion>"
    },
    "name": "set_workflow_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowIdYesWorkflow id, from list_workflows or set_up_workflow
baseVersionYesThe current version number the change starts from
targetLanguagesYesEvery target locale the Workflow should declare, e.g. ["fr", "de"]

Output Schema

NameRequiredDescriptionDefault
workflowYes
publishedYesfalse when the languages were already these: no version was published
takeoversYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructive/openWorld annotations by disclosing the version-publishing model, the optimistic-concurrency guard with its exact error code, and the no-op case (identical languages return published: false). These are the behavioral traits that determine whether an agent can call it safely and interpret the result.

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?

Front-loaded with the action and its effect, followed by the concurrency rule and the no-op case in a logical order. The closing sentence about showing names and locales rather than UUIDs is useful but is presentation guidance that sits slightly apart from the tool's mechanics.

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?

For a destructive, version-publishing mutation with an output schema already present, the description covers effect scope, concurrency behavior, idempotency, and the output flag. Nothing an agent needs in order to invoke it correctly or explain the outcome is missing.

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 100%, so the schema already carries the per-parameter text; the description still adds meaning by framing baseVersion as the starting version that must equal the current one and targetLanguages as the complete replacement set. The addition is real but modest beyond the schema.

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 — 'Replace the target languages a Workflow declares' — and pins the scope further with 'publishing its next version with nothing else changed', which makes the whole-set replacement semantics unambiguous versus an incremental add. An agent knows exactly what changes and what does not.

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?

Clear operational context: baseVersion must come from get_workflow, and a concurrent publish yields WORKFLOW_BASE_VERSION_STALE. It does not explicitly name a sibling alternative (e.g. when to use set_up_workflow instead), so it stops short of full when/when-not routing.

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

All globalize.now 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