Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Open Swarm Spaces

swarm_open_spaces
Read-onlyIdempotent

Show a visual Space browser in an MCP Apps capable host using the ui://swarm/spaces-v1.html resource. Returns the same authorized Space page as swarm_list_spaces without launching a browser or creating a session. Use swarm_list_spaces if the host cannot render MCP Apps, or for data only. limit, order and cursor control the initial Space page; the host loads Runs and Artifacts as requested.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size; follow next_cursor for more.
orderNoasc or desc; retain the same order across pages.
cursorNoPrevious next_cursor; keep filters and order.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Previous next_cursor; same filters and order."New value: +"Previous next_cursor; keep filters and order."
    • 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."
  2. Changed3 schema fields changed
    • 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."
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds real context beyond them: it does not launch a browser or create a session, and the host lazy-loads Runs and Artifacts. It stops short of saying how a non-capable host fails (error vs fallback), so a 4 rather than 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 tightly packed sentences, front-loaded with what the tool does, then the fallback routing, then parameter scoping. No filler or repetition of schema/annotation data.

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?

Output schema exists so return values need no explanation; annotations cover the safety profile; the description covers the host requirement, the UI resource, the sibling equivalence, and pagination scope. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema doesn't: limit/order/cursor govern only the *initial* Space page, with Runs and Artifacts loaded on demand by the host. That scoping insight is genuinely useful for pagination decisions.

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 ('Show a visual Space browser') plus the UI resource it renders, and explicitly distinguishes itself from swarm_list_spaces by noting it returns the same authorized Space page. An agent can tell immediately this is the visual/UI variant rather than a data-fetch tool.

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 alternative and the selecting condition: 'Use swarm_list_spaces if the host cannot render MCP Apps, or for data only.' This is a clear when-to-use / when-not-to-use rule tied to the host's capabilities.

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