Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Inspect runtime (advanced)

swarm_get_core
Read-onlyIdempotent

Inspect a saved device or Cloud runtime's capabilities, limits and configuration before targeting it. Find IDs with swarm_list_cores; use swarm_get_core_health for recorded readiness. Normal MCP agents need no Core.

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": {
      "core_id": "<core_id>"
    },
    "name": "swarm_get_core"
  }
}

Input Schema

NameRequiredDescriptionDefault
core_idYesExact ID from swarm_list_cores; no fallback.
space_idNoSpace ID from swarm_list_spaces; omit if sole.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / core_id / description
      Previous value: -"Exact runtime ID from swarm_list_cores; no fallback."New value: +"Exact ID from swarm_list_cores; no fallback."
    • 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."
  2. Changed2 schema fields changed
    • addedInput schema / properties / core_id / description
      Added value: +"Exact runtime ID from swarm_list_cores; no fallback."
    • addedInput schema / properties / space_id / description
      Added value: +"Omit for a single approved Space."
  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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description's only added behavioral signal is that the tool is "advanced" and unnecessary for ordinary agents, which is more usage framing than behavior; it says nothing about latency, auth, or result shape. With annotations and an output schema doing the heavy lifting, a 3 is appropriate.

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, then ID discovery, then the alternative and the necessity caveat. Every clause earns its place and the most decision-relevant information is front-loaded.

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?

For a read-only inspection tool with a full output schema and fully documented two-parameter schema, nothing an agent needs to call it correctly is missing — purpose, ID sourcing, sibling alternatives, and even a relevance caveat are all present.

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 both parameters carry their own descriptions, including the "no fallback" constraint and the space-omission rule. The description reinforces core_id by pointing to swarm_list_cores, but adds no syntax or scoping detail beyond the schema, so the baseline 3 holds.

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 (inspect) and resource (a saved device or Cloud runtime) and enumerates what it returns: capabilities, limits, and configuration. It also positions itself against siblings by naming swarm_list_cores for ID discovery and swarm_get_core_health for readiness, so an agent can distinguish 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?

Gives explicit timing ("before targeting it"), routes to the two relevant alternatives with their distinct purposes, and even includes a when-not signal: "Normal MCP agents need no Core." That is about as complete a usage statement as a tool can carry.

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