Skip to main content
Glama
Sign In

secondbrain

by media.secondbrain
OverviewDiscussionsAdmin

start_artifact_upload

Guarda un artefacto sin retipearlo: el archivo va del disco a Secondbrain sin pasar por el modelo.

Para cuando el archivo ya existe en disco. **Sólo artefactos LIVIANOS: hasta 20 KB.** Medí el archivo ANTES (`wc -c ARCHIVO`) y pasalo en `bytes`. Si pasa de 20 KB no lo intentes por ningún camino del MCP: decile al usuario que lo guarde con la extensión de Chrome de Secondbrain (pestaña «Artefactos» → «Sincronizar»).

Devuelve una upload_url. El PUT la termina: sube el archivo Y crea la versión de una. NO hay segundo llamado.

  curl -X PUT "<upload_url>" --data-binary @mi-artefacto.html

Con artifact_id agrega una versión nueva a uno que ya existe; sin él crea uno nuevo.

Input Schema

NameRequiredDescriptionDefault
nameYesNombre del artefacto
tipoNoQué es el contenido del archivo (default: html)
bytesYesCuánto pesa el archivo, en bytes (`wc -c ARCHIVO`). Se valida ANTES de subir: arriba del tope no se guarda.
origenNo
artifact_idNoPara actualizar uno existente
document_idNoDocumento del que cuelga
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. Changed2 schema fields changed
    • addedInput schema / properties / bytes
      Added value: +{
+  "description": "Cuánto pesa el archivo, en bytes (`wc -c ARCHIVO`). Se valida ANTES de subir: arriba del tope no se guarda.",
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "bytes"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (which only say not-readOnly, not-destructive, closed-world), the description discloses the return value (upload_url), that the PUT both uploads and creates the version in one call with no second call, and that bytes is validated before upload. That is exactly the non-obvious flow an agent needs.

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?

Front-loaded purpose sentence, then conditions, then the curl example, then the create-vs-update rule — a good ordering. The 20 KB limit is stated twice (bold rule plus the 'si pasa de 20 KB' branch), which costs a little tightness.

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?

No output schema exists, and the description covers what is returned (upload_url), how to finish the operation, and that no follow-up call is needed. Combined with the 86% schema coverage, an agent has everything required to invoke it correctly.

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 already 86%, yet the description still adds meaning: how to obtain `bytes` (`wc -c`), that exceeding the cap aborts the upload, and that `artifact_id` switches from 'create new' to 'add a new version to an existing artifact'. Minor fields (tipo, origen, document_id) are left to the schema.

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?

Specific verb and resource (guarda un artefacto desde disco, sin pasar por el modelo) with the key differentiator 'sin retipearlo' against sibling save_artifact. It doesn't name the siblings explicitly, but an agent can tell it starts an upload flow rather than completing one.

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 ('Para cuando el archivo ya existe en disco'), a hard precondition (≤20 KB, measure with `wc -c` first), and an explicit when-NOT plus redirect to the Chrome extension if the file is too big. It even warns not to try any other MCP path, which routes the agent away from siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All secondbrain toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources