Skip to main content
Glama

Get artifact

get_artifact
Read-onlyIdempotent

Inspect an authorized generated artifact's metadata, checksum, lineage and protected download link.

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": "get_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifact_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: access is gated to artifacts the caller is authorized to see, and the returned download link is "protected" rather than a plain URL, which signals a credential or expiry constraint the agent would not otherwise know.

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?

A single front-loaded sentence with no filler; the scope qualifier ("authorized") and the returned field list both earn their place. Nothing is repeated from the schema 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?

This is a simple one-parameter read tool with an output schema, rich annotations, and a description that covers what comes back. The only real gap is failure behavior — what happens when the artifact is missing or the caller lacks authorization — which an agent would need to handle.

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 0%, so the description must carry the load for the single artifact_id parameter. It does add some meaning — the id must identify a generated artifact and one the caller is authorized for — but gives no format, example, or behavior for invalid/unauthorized ids.

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?

States a specific verb and resource ("Inspect an authorized generated artifact") and enumerates the concrete fields returned: metadata, checksum, lineage, and a protected download link. The word "generated" plus "artifact" distinguishes it reasonably well from siblings like get_asset or get_dataset, though it never explicitly says so.

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

Usage Guidelines2/5

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

There is no when-to-use framing, no prerequisites stated beyond the adjective "authorized," and no reference to any alternative (e.g., get_asset, get_dataset, list_projects). An agent must infer from the field list that this is the tool to call when it already holds an artifact_id and needs provenance/checksum data.

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