Skip to main content
Glama

Versions of my website

versiones_web
Idempotent

Use this when the person wants to see earlier states of their palimpalem website or go back to one. Requires palimpalem sign-in. Without restore it lists the saved versions (each is the state before a change); with restore= it brings that state back, after saving the current state as a new version, so nothing is lost.

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": "versiones_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
webYesThe website: its name, its palimpalem address or its own domain.
restoreNoOptional. Id of the version to bring back, from the list (e.g. 1763030000.1234).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With annotations already declaring readOnlyHint=false and destructiveHint=false, the description adds real value: it discloses the sign-in requirement, explains that each listed version is the state before a change, and clarifies that a restore first saves the current state as a new version so nothing is lost. The only soft spot is that this side effect sits slightly at odds with idempotentHint=true, since repeating a restore would keep appending versions.

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?

Two sentences, front-loaded with the usage trigger and followed by the mode behavior, with zero filler. The prerequisite and the two operating modes are covered without repetition.

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, the description covers both operating modes, the auth requirement, and the write side effect of restoring. It could say a bit more about what the returned version list looks like, but that is a minor gap given the annotations already carry the safety profile.

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 defines both parameters; the baseline would be 3. The description goes further by explaining that the optional restore parameter switches the tool from listing to restoring, and that its id comes from the list — meaningful mode semantics beyond the field documentation.

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 states a concrete verb and resource — viewing earlier states of a palimpalem website and restoring one — and makes the dual mode explicit. It is clear enough to distinguish from editing (editar_web) or viewing the live site, though it does not name any sibling to sharpen that boundary.

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?

"Use this when the person wants to see earlier states ... or go back to one" gives an explicit trigger condition and an authentication prerequisite (palimpalem sign-in). It stops short of naming when NOT to use it or pointing to an alternative for related tasks, so it is clear context rather than full routing guidance.

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.