Skip to main content
Glama

save_artifact_from_url

Destructive

Guarda un artefacto que el SERVIDOR se baja de una URL. Ni retipeás el contenido ni tenés que poder alcanzar el storage.

Hace un GET HTTPS al enlace crudo del archivo, el «Raw» de GitHub (https://docs.github.com/en/repositories/working-with-files/using-files/viewing-and-understanding-files). Para cuando el archivo YA está publicado en uno de estos hosts: raw.githubusercontent.com, gist.githubusercontent.com, objects.githubusercontent.com. Tiene que ser el enlace directo al contenido crudo, sin redirecciones.

**Sólo artefactos LIVIANOS: hasta 20 KB.** Uno más pesado se rechaza: va por la extensión de Chrome de Secondbrain.

OJO: no sirve para publicarlo vos. En los sandboxes de Claude la ESCRITURA en GitHub está bloqueada por el proxy ("Gist writes are not permitted"), y un repo privado tampoco sirve porque el servidor no tiene token. Y no publiques contenido sensible en un repo público para esquivar esto: se scrapea y se cachea. Si el contenido no se puede publicar y es liviano, usá 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": {
      "name": "<name>",
      "url": "<url>"
    },
    "name": "save_artifact_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL RAW del archivo
nameYesNombre del artefacto
notaNo
tipoNo
origenNo
artifact_idNoPara actualizar uno existente
document_idNo
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 flag a destructive, open-world, non-idempotent write, and the description adds real context beyond them: a GET is performed server-side, redirects are not followed, the 20KB ceiling comes from the transport itself, sandbox proxies block Gist writes, private repos fail for lack of a token, and public-repo workarounds get scraped and cached. What it omits is what happens on overwrite when artifact_id is supplied, so it falls short of a 5.

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?

The core mechanic and the host whitelist are front-loaded before the caveats, and every paragraph carries a distinct constraint. The inline link to GitHub's 'Raw' documentation is the one piece that could be trimmed without losing actionable information.

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 destructive, open-world write with no output schema and 8 parameters, the description supplies the failure modes an agent needs (size rejection, redirect rejection, sandbox proxy block, no private-repo token) and routes to fallbacks. Nothing required to decide whether to call it is missing.

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 coverage is 50%, and the description only illuminates the url parameter indirectly (raw link, whitelisted hosts, no redirects). It says nothing about tipo, origen, nota, document_id or artifact_id semantics, so half the parameters remain undocumented in both places; the added meaning is real but partial.

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 opening line states a specific verb and resource with the defining mechanic: 'Guarda un artefacto que el SERVIDOR se baja de una URL', plus the explicit contrast that the user neither retypes content nor needs storage access. This lets an agent separate it from save_artifact without opening either 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?

Explicit when-to-use (file already published at raw.githubusercontent.com, gist.githubusercontent.com, objects.githubusercontent.com, direct raw link, no redirects), explicit limit (>20KB rejected, use the Chrome extension), and an explicit alternative for the blocked case ('Si el contenido no se puede publicar y es liviano, usá save_artifact'). Both the positive and negative routing conditions are named.

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