Skip to main content
Glama

Languages of my website

idiomas_web
Idempotent

Use this when the person wants their palimpalem website in another language as well, or wants to remove one. Requires palimpalem sign-in. action=list shows the languages; action=add translates every page by AI in the background (about one minute per page) and publishes it under // with a language switch, and later changes are translated automatically; action=remove takes a language off. The original language stays the one that is edited. Languages: es, en, de, fr, it, pt, ca.

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": {
      "web": "<web>"
    },
    "name": "idiomas_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
webYesThe website: its name, its palimpalem address or its own domain.
actionNolist
languageNoNeeded for add and remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say the tool is non-read-only, idempotent, non-destructive and non-open-world; the description goes well beyond that. It discloses the sign-in requirement, that add runs AI translation in the background at roughly one minute per page, that output is published under /<code>/ with a language switch, that later edits are re-translated automatically, and that the original language remains the edited one. That is exactly the behavioral context an agent needs before committing a user to a long-running job.

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?

It is a single dense paragraph, front-loaded with the trigger condition before enumerating the actions, and every clause adds information (timing, URL layout, edit semantics, code list). It is slightly run-on and would read better as a short bulleted action breakdown, but nothing is wasted.

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 three-parameter mutation tool with no output schema, the description is thorough: auth, timing, published path, ongoing behavior and the original-language rule are all covered. Remaining gaps are what list actually returns and whether remove permanently drops translated content, which a cautious agent would still want to know.

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 67% and the description compensates by explaining what each action value means, including the asynchronous consequence of add and the effect of remove, and by repeating the supported language codes that the enum restricts. The web parameter is left to its schema description ('name, palimpalem address or own domain'), which is adequate, so this is meaningfully above the schema alone but not exhaustively annotated.

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 names a specific resource (the palimpalem website's languages) and specific operations (list, add, remove), and it opens with the exact user intent that should trigger it. An agent can distinguish this from 'editar_web' or 'publicar_web' without inspecting either schema, since language management is an explicit, separate concern here.

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 first sentence gives a clear when-to-use condition: the person wants the site in another language or wants to remove one. It also implicitly says when not to use it by tying each action to a distinct intent, but it never names a sibling tool or states an exclusion (for example, that it is not the tool for changing the site's original language).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.