Skip to main content
Glama

append_artifact

Agrega contenido AL FINAL de un artefacto ya guardado, sin retipearlo. Para lo que crece por abajo: una sección nueva, una fila más, una entrada de log.

El contenido va como HTML (es lo que hay guardado) y se inserta justo antes de `</body>`, que es donde tiene que ir para que la página siga siendo válida; si el archivo no tiene `</body>`, se pega al final.

Para cambiar algo que YA está escrito, patch_artifact. Para reemplazar el artefacto entero, save_artifact.

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": {
      "artifact_id": "<artifact_id>",
      "contenido": "<contenido>"
    },
    "name": "append_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
notaNoQué se agregó, en una línea. Se lee en el historial.
contenidoYesEl HTML que se agrega al final
artifact_idYesID del artefacto
base_versionNoExigir que la versión viva sea esa; si no, se rechaza.
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent write, so the bar is lower; the description still adds genuinely non-obvious mechanics — content is HTML and lands immediately before </body>, falling back to end-of-file when no </body> exists. It stops short of warning about duplicate appends (consistent with idempotentHint=false) or what happens if artifact_id is stale, so it is not a full behavioral picture.

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?

Three short blocks: what it does, the insertion mechanics, then the alternatives. The critical constraint is front-loaded in capitals and every sentence carries distinct information with zero filler.

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 five-parameter mutation with no output schema, the description covers the risky, non-obvious part (insertion point and fallback) and the routing to siblings. It omits failure/conflict behavior around base_version and whether the response returns a new version number, minor given the schema coverage.

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 the schema already documents all five parameters including base_version's rejection semantics and workspace_id resolution. The description only reinforces that contenido is HTML, which the schema states anyway, and says nothing extra about nota or base_version.

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?

Specific verb plus resource ("Agrega contenido AL FINAL de un artefacto ya guardado") with the scope constraint in capitals, and it explicitly separates itself from patch_artifact and save_artifact. An agent can tell it apart from the two nearest siblings 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the positive case ("Para lo que crece por abajo: una sección nueva, una fila más, una entrada de log") and names both alternatives with the condition that selects them: patch_artifact for editing existing text, save_artifact for full replacement. Nothing is left to inference.

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.

Resources