Swarm

List intelligence projections

swarm_list_projections

Read-onlyIdempotent

Inspect saved knowledge projections, their source Artifact IDs, validation scores and status. Use swarm_get_learning_frontier for an overview. Results are stored evidence, not newly recomputed or promoted knowledge.

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

Input Schema

Name	Required	Description
`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.
`family`	No	Existing knowledge-family key filter.
`status`	No	Status filter; use values returned for this resource.
`space_id`	No	Space ID from swarm_list_spaces; omit if sole.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 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 / family / description

Added value: +"Existing knowledge-family key filter."

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."

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."

addedInput schema / properties / status / description

Added value: +"Status filter; use values returned for this resource."

Changed4 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 / space_id / description
```
Added value: +"Omit for a single approved Space."
```
First observedOct 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive, so the safety profile is free. The description still earns credit by disclosing provenance semantics: results are stored evidence, not recomputed or promoted knowledge — a freshness guarantee an agent cannot infer from annotations or schema. Pagination behavior is left to the schema rather than repeated here.

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, zero filler, with the purpose front-loaded and the routing hint and provenance caveat following in priority order. Nothing is repeated from the schema or annotations.

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?

An output schema exists, so return shape need not be described; pagination and filters are fully covered by the schema; annotations carry the safety profile. What remains — what the tool is for, which sibling to prefer, and whether the data is live — is all stated.

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 every parameter (limit, order, cursor, family, status, space_id) is documented inline, including cross-page ordering and cursor reuse. The description adds nothing parameter-specific, so the baseline 3 applies. Note that status and family lack enums, but the schema already tells the caller to use values returned for this resource.

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 and resource (inspect saved knowledge projections) plus the fields surfaced (source Artifact IDs, validation scores, status), which is more than a restatement of the title. It explicitly names a sibling it is not (swarm_get_learning_frontier). It stops short of saying this is a paginated list operation, though the plural resource and schema imply it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use swarm_get_learning_frontier for an overview" names an alternative and the condition that selects it, and the closing sentence draws a boundary on what the results are not. No exclusions against the many swarm_list_* siblings (artifacts, learning_candidates, evaluations), which would have made it a 5.

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.