Skip to main content
Glama

Publish my website

publicar_web
Idempotent

Use this when the person wants their palimpalem website to be visible to everyone, e.g. after maintenance mode. Requires palimpalem sign-in. Without confirm=true it only reports what would happen and changes nothing; with confirm=true (only after the person agreed) it publishes and returns the live address.

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

Input Schema

NameRequiredDescriptionDefault
webYesThe website: its name, its palimpalem address or its own domain.
confirmNotrue only after the person has confirmed that the website should go public.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, openWorldHint=true) it discloses the sign-in requirement, the default dry-run that changes nothing, the irreversible step that actually publishes, and that a live address is returned. These are exactly the mutation-side facts the annotations do not carry.

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 trigger, then the auth prerequisite and the confirm contract. No redundant restatement of the tool name or title, and nothing that could be cut without losing meaning.

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 two-parameter publish tool with no output schema, the description covers the precondition (sign-in), the safe default, the confirming step, and the return value (live address). An agent has everything needed to call it correctly and safely.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: it spells out the dry-run vs. live-publish contract of confirm and that confirm should only be set after the person agreed. That is a genuine behavioural rule layered on top of the schema text.

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 ('their palimpalem website to be visible to everyone') plus a concrete triggering scenario ('after maintenance mode'). An agent can distinguish this publish action from siblings like crear_borrador_web, editar_web, or ver_mi_web without opening any schema.

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 when-to-use condition ('when the person wants their website to be visible to everyone') and a representative case (maintenance mode). It does not explicitly name a sibling alternative or state a when-not condition, which keeps it just short of a 5.

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.