Skip to main content
Glama

artifact_registry

Read-only

Lists fixture-backed metadata for every X++ artifact type and explicitly identifies unavailable types, helping you confirm supported artifacts before editing or syncing.

Instructions

List all fixture-backed artifact metadata and explicitly unavailable types.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
artifactsNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add one real behavioral fact beyond that — results are fixture-backed and include explicitly unavailable types — but says nothing about ordering, size, or how unavailability is represented.

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?

A single front-loaded sentence with no padding or repetition. It is dense to the point of opacity in the phrase "explicitly unavailable types," but every clause carries information.

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 zero-parameter, read-only listing tool with a full output schema, the description covers what the call returns and that unavailable types appear in the result. Remaining ambiguity about what "fixture-backed" means is the main shortfall.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims conflict with the empty object 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?

States a specific verb (List) and resource (artifact metadata), and adds scope detail — fixture-backed metadata plus explicitly unavailable types — that separates it from siblings like artifact_build or artifact_validate. The term "fixture-backed" is unexplained jargon and "unavailable types" is ambiguous, keeping it below a 5.

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?

The description never says when to use this versus artifact_design or artifact_validate, nor does it state exclusions or prerequisites. Only the verb "List" implies a discovery role, so the agent must infer the routing decision.

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