Swarm

List Artifacts

swarm_list_artifacts

Read-onlyIdempotent

Browse metadata by kind, repository or Run. Use swarm_get_artifact for details, swarm_get_artifact_content for the body. No bulk payload download.

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

Input Schema

Name	Required	Description
`kind`	No	Kind filter from this resource's list or contract.
`limit`	No	Page size; follow next_cursor for more.
`order`	No	asc or desc; retain the same order across pages.
`cursor`	No	Previous next_cursor; keep filters and order.
`run_id`	No	Run ID from swarm_list_runs.
`space_id`	No	Space ID from swarm_list_spaces; omit if sole.
`repository_id`	No	Existing source-repository ID filter.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 29, 2026

changedInput schema / properties / cursor / description

Previous value: -"Previous next_cursor; same filters and order."New value: +"Previous next_cursor; keep filters and order."

addedInput schema / properties / kind / description

Added value: +"Kind filter from this resource's list or contract."

changedInput schema / properties / limit / description

Previous value: -"Page size."New value: +"Page size; follow next_cursor for more."

changedInput schema / properties / order / description

Previous value: -"Paging order."New value: +"asc or desc; retain the same order across pages."

addedInput schema / properties / repository_id / description
```
Added value: +"Existing source-repository ID filter."
```

changedInput schema / properties / run_id / description

Previous value: -"ID from launch or swarm_list_runs."New value: +"Run ID from swarm_list_runs."

changedInput schema / properties / space_id / description

Previous value: -"Omit for a single approved Space."New value: +"Space ID from swarm_list_spaces; omit if sole."

Changed5 schema fields changedOct 29, 2026
- addedInput schema / properties / cursor / description
```
Added value: +"Previous next_cursor; same filters and order."
```
- addedInput schema / properties / limit / description
```
Added value: +"Page size."
```
- addedInput schema / properties / order / description
```
Added value: +"Paging order."
```
- addedInput schema / properties / run_id / description
```
Added value: +"ID from launch or swarm_list_runs."
```
- addedInput schema / properties / space_id / description
```
Added value: +"Omit for a single approved Space."
```
First observedOct 28, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered without the description. The description's one genuine addition is 'No bulk payload download,' which tells the agent results are metadata-only and must be followed up per item. It says nothing about pagination behavior, default page size, or ordering stability beyond what the schema already carries.

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?

Three short sentences, front-loaded with what the tool does, then routing, then the one exclusion. No filler, no restatement of the name, and every clause carries information an agent would otherwise have to guess.

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?

An output schema exists, so return shape needn't be explained, and the schema covers filters and cursor-based paging. The description supplies the sibling routing and the metadata-only constraint, which is enough to call the tool correctly. Only marginal gaps remain, such as whether run_id and repository_id can be combined.

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 all seven parameters (kind, limit, order, cursor, run_id, space_id, repository_id) are already documented with sourcing hints. The description echoes the filter dimensions but adds no syntax, format, or interaction detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 verb (browse) and resource (artifact metadata) plus the three filter axes: kind, repository, and Run. It explicitly names the two sibling tools it is not, so an agent can separate listing from fetching. It stops short of 5 only because the word 'artifact' never appears in the description itself; the resource is inferred from the name and title.

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 routes the agent precisely: 'Use swarm_get_artifact for details, swarm_get_artifact_content for the body,' naming both alternatives and the condition that selects each. The closing 'No bulk payload download' rules out the misuse case where an agent might try to fetch content through this list endpoint.

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

All Swarm tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.