Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Get Artifact sources

swarm_get_artifact_sources
Read-onlyIdempotent

Trace an Artifact's source references before relying on its content. Use swarm_get_artifact_content for the body. Cross-Space references require source-Space access and can be omitted when unavailable.

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_sources"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds a genuinely useful behavioral trait beyond that: cross-Space references require source-Space access and may be omitted, warning the agent that results can be partial. It stops short of saying whether tracing is recursive or how references are ordered, so not quite a 5.

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 with zero waste: purpose first, alternative second, caveat third. Every sentence earns its place and the most decision-relevant content is 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 an output schema present, return values need not be explained, and the description covers purpose, the sibling alternative, and the partial-result caveat. Minor gap: it does not state whether tracing is one-hop or transitive, which affects how an agent interprets the source list.

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 100% and the single parameter already documents its own provenance ('Artifact ID from swarm_list_artifacts'), so the schema does the heavy lifting. The description adds no format, validation, or handling detail for artifact_id beyond what the schema provides, which is the baseline-3 case.

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 and resource ('Trace an Artifact's source references') and immediately separates itself from the sibling that returns the body. An agent can distinguish this from swarm_get_artifact and swarm_get_artifact_content 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?

Gives an explicit usage condition ('before relying on its content') and names the alternative tool plus what it is for ('Use swarm_get_artifact_content for the body'). Nothing about tool selection is left 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