Skip to main content
Glama

Get an artifact

get_artifact
Read-onlyIdempotent

One artifact's content: a workbook's sheets, a document's blocks or a deck's slides, with the address of its page, where its file is downloaded.

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": {
      "id": "<id>"
    },
    "name": "get_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe artifact's id, from make_artifact or list_artifacts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful return-shape context (page address, download location) but says nothing about invalid ids, size limits, or whether fetching has side effects on the stored artifact.

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?

One dense sentence with the payload described first and the ancillary locations trailing. The clause 'with the address of its page, where its file is downloaded' is slightly awkward but still short and front-loaded.

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 no output schema, the description carries the burden of describing returns, and it does so at a high level by naming the per-type content shape plus page address and download location. Given a single fully documented parameter and complete annotations, this is close to sufficient, with only error and limit behavior left unstated.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains the id comes from make_artifact or list_artifacts. The description adds no syntax, format, or sourcing detail beyond that, so the baseline of 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 states a specific resource and scope: the content of one artifact, fetched by id, with type-specific structure named (workbook sheets, document blocks, deck slides). It is clearly distinguishable from list_artifacts and make_artifact, though the verb itself is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: you call this when you already have an artifact id and need its content. There is no explicit when-to-use versus list_artifacts or preview_table, and no stated prerequisites or failure conditions.

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