Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Get Artifact

swarm_get_artifact
Read-onlyIdempotent

Read metadata, hash and availability using an ID from swarm_list_artifacts. Fetch the body with swarm_get_artifact_content; provenance with swarm_get_artifact_sources.

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

Input Schema

NameRequiredDescriptionDefault
artifact_idYesArtifact ID from swarm_list_artifacts.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / artifact_id / description
      Previous value: -"ID from swarm_list_artifacts or a result."New value: +"Artifact ID from swarm_list_artifacts."
  2. Changed1 schema field changed
    • addedInput schema / properties / artifact_id / description
      Added value: +"ID from swarm_list_artifacts or a result."
  3. First observed

TDQS

A4.3/5.0
Behavior3/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 fully covered. The description adds the boundary of what is returned (metadata/hash/availability rather than the body), but says nothing about failure behavior for unknown IDs or the shape/size of the response. With annotations doing the heavy lifting, this is adequate but not rich.

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 tight sentences, zero redundancy. The core purpose is front-loaded, followed by the sibling routing needed to act correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, a fully documented single parameter, and complete annotations, the description supplies everything else an agent needs: the ID source and the routing to body/provenance tools.

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% and the single parameter already documents its origin and pattern constraints. The description only repeats the source (swarm_list_artifacts) without adding format or validation detail, so the 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 (read) plus the exact resource scope (metadata, hash, availability) and the required ID source. It explicitly distinguishes itself from swarm_get_artifact_content and swarm_get_artifact_sources, so an agent can select it without opening any schema.

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?

Names both alternatives and the condition that selects each: body goes to swarm_get_artifact_content, provenance to swarm_get_artifact_sources. It also states the prerequisite for the ID (from swarm_list_artifacts), leaving nothing to inference.

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

All Swarm toolsInspect
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.

Resources