Swarm

List promotion gates

swarm_list_promotion_gates

Read-onlyIdempotent

Trace recorded promotion decisions by candidate_id, projection_id or decision. Use when checking why knowledge was accepted or held. Reading does not approve or promote it.

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

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.
`decision`	No	Decision key from a recorded promotion gate.
`space_id`	No	Space ID from swarm_list_spaces; omit if sole.
`candidate_id`	No	Candidate ID from swarm_list_learning_candidates.
`projection_id`	No	Projection ID from swarm_list_projections.

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 / candidate_id / description

Previous value: -"Learning candidate ID from swarm_list_learning_candidates."New value: +"Candidate ID from swarm_list_learning_candidates."

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 / decision / description

Added value: +"Decision key from a recorded promotion gate."

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 / projection_id / description

Previous value: -"Knowledge projection ID from swarm_list_projections."New value: +"Projection ID from swarm_list_projections."

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

Changed6 schema fields changedOct 29, 2026
- addedInput schema / properties / candidate_id / description
```
Added value: +"Learning candidate ID from swarm_list_learning_candidates."
```
- 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 / projection_id / description
```
Added value: +"Knowledge projection ID from swarm_list_projections."
```
- addedInput schema / properties / space_id / description
```
Added value: +"Omit for a single approved Space."
```
First observedOct 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds domain-relevant reassurance that reading gates does not itself approve or promote — valuable because the resource name implies decision-making power — but says nothing about pagination behavior or result scope.

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 the action and filters, then the usage cue, then the side-effect clarification. Nothing is redundant and no sentence could be dropped without losing content.

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 values need not be described, annotations cover the safety profile, and the schema documents all seven filters fully. The description is adequate for calling the tool correctly; only filter-combination behavior and result ordering semantics are left implicit.

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 every parameter already carries its own documentation including ID provenance hints. The description only restates the three filter dimensions ('by candidate_id, projection_id or decision') without adding format or combination semantics (e.g., whether filters AND together). Baseline 3 applies.

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 ('Trace') and specific resource ('recorded promotion decisions') and names the three filter keys, which is enough to separate it from the many swarm_list_* siblings. It doesn't explicitly contrast with swarm_list_learning_candidates or swarm_list_projections, but the resource is distinct enough.

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 when checking why knowledge was accepted or held' gives a clear triggering scenario, and 'Reading does not approve or promote it' sets an expectation boundary. No explicit named alternative is offered, but the usage context is concrete rather than implied.

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.