Skip to main content
Glama

finish_artifact_upload

Idempotent

Ya casi nunca hace falta: el PUT de start_artifact_upload deja el artefacto guardado solo. Queda para las subidas viejas, que dejaban el archivo esperando. Si no hay nada esperando, te dice en qué versión quedó el artefacto y listo.

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>"
    },
    "name": "finish_artifact_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
notaNoQué cambió en esta versión, en una línea
artifact_idYesEl id que devolvió start_artifact_upload
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description still adds real behavioral context: on the degenerate case where nothing is pending, the call is a no-op that reports the artifact's resulting version, which is exactly the kind of idempotent-fallback detail annotations cannot express. It does not mention permission or workspace-scoping requirements.

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?

Three short sentences that are correctly front-loaded with the most decision-relevant fact (almost never needed), followed by the reason and the edge-case behavior. The tone is conversational but no sentence is 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?

With a fully documented 3-parameter schema and annotations covering the safety profile, the description only needed to explain the deprecation context and the fallback outcome, and it does both. There is no output schema, and the return information (the resulting version) is at least gestured at, though not fully specified.

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 artifact_id, workspace_id and nota are already documented in the schema. The description adds nothing about how the parameters behave in the legacy flow, so the baseline 3 applies.

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?

The description conveys that this tool closes out a pending artifact upload, and it clearly distinguishes itself from start_artifact_upload by explaining that the PUT already saves the artifact. It never states the action plainly ('finaliza la subida pendiente'), relying instead on inference from 'las subidas viejas, que dejaban el archivo esperando' and the fallback of reporting the resulting version.

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?

It gives an explicit when-not ('ya casi nunca hace falta'), names the alternative path that replaces it (the PUT in start_artifact_upload), and defines the narrow remaining case (legacy uploads that left the file waiting). An agent can decide correctly without opening any other schema.

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