Skip to main content
Glama

list_artifacts

Read-onlyIdempotent

Lista los artefactos guardados del workspace: id, nombre, tipo, qué modelo lo hizo, versión actual y de qué documento cuelga. Para actualizar uno, usar su id en save_artifact.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
document_idNoSólo los que cuelgan de este documento
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by specifying the returned field set (model that produced it, current version, parent document), which substitutes for the missing output schema. It omits pagination/default behavior, keeping it 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences: the first front-loads what is listed and which fields are returned, the second handles redirection. No redundant restatement of the tool name or annotations.

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 read-only list tool with no output schema, describing the returned fields fills the main gap, and the update-redirect closes the other. Only the limit/pagination behavior (default 50, max 200) is left purely to the parameter schema.

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%, including the important note that omitting workspace_id returns ALL of the person's workspaces, so the schema already carries the semantics. The description mentions workspace scoping only indirectly ('del workspace'), adding nothing beyond the schema; baseline 3 applies.

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+resource ('Lista los artefactos guardados del workspace') and enumerates exactly which fields come back (id, nombre, tipo, modelo, versión, documento padre), so the agent knows both what it does and what it yields without opening the 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?

Explicitly routes the mutation case elsewhere: 'Para actualizar uno, usar su id en save_artifact', which prevents the agent from attempting an update via this tool. It gives no guidance on when listing is preferable to other listing tools (e.g. list_workspaces), but it establishes clear context for both use and exclusion of the write path.

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