Skip to main content
Glama

Save a draft as my website

reclamar_borrador
Idempotent

Use this when the person likes a draft from crear_borrador_web and wants to keep it as their own website. Requires palimpalem sign-in. Creates a new free website in their account from the draft (it never overwrites an existing website) and returns its address, e.g. https://name.palimpalem.com/. The login details are e-mailed to the person. Calling it again with the same draft returns the same website.

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": {
      "draft": "<draft>"
    },
    "name": "reclamar_borrador"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYesThe draft link (https://palimpalem.com/palim/apli/entwurf.php?t=...) or its 24-character token.
subdomainNoOptional. Wished address name, e.g. panaderia-ruzafa for panaderia-ruzafa.palimpalem.com. Letters a-z, digits and hyphens, 3 to 25. Without it a name is suggested from the business name.

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?

Goes well beyond the annotations: discloses the sign-in requirement, guarantees it never overwrites an existing website (reinforcing destructiveHint=false with concrete semantics), states that login details are e-mailed, and confirms repeat calls return the same website.

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 usage condition, then the side effects, then the return value, in four tight sentences with no redundant wording.

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?

With no output schema, the description supplies the return value and its format, plus auth, email delivery, overwrite protection and idempotency — everything an agent needs to call it and report the result.

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 description coverage is 100%, so both the draft link/token format and the subdomain constraints are already documented. The description adds no further meaning about parameter interaction, so the baseline of 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?

States a specific verb and outcome — 'Creates a new free website in their account from the draft' — and explicitly positions it relative to crear_borrador_web, so an agent can distinguish drafting from saving a draft as a live site.

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?

Gives a clear trigger ('Use this when the person likes a draft from crear_borrador_web and wants to keep it as their own website'), naming the prerequisite sibling. It does not explicitly say when not to use it or point to publicar_web as the follow-up step, so it falls short of 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.