Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Inspect runtime readiness (advanced)

swarm_get_core_health
Read-onlyIdempotent

Inspect saved setup and heartbeat evidence for a device or Cloud Core from swarm_list_cores. Use before targeting that runtime, and read timestamps rather than assuming it is currently online. Use swarm_list_agent_participants for connected-agent eligibility. This read does not ping, enroll or resume a runtime.

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

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

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds information annotations cannot convey: the evidence is 'saved' and may be stale, so timestamps must be read rather than inferred as live status. The closing sentence rules out side effects the agent might otherwise assume ('does not ping, enroll or resume a runtime'), which is exactly the kind of negative capability disclosure that prevents misuse.

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 in a deliberate order: what it returns, how to use it, then what it does not do. No restatement of the name or title, and every clause adds decision-relevant information.

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 values need no prose, and rich annotations cover the safety profile. What remains — staleness of the evidence, prerequisite listing tool, alternative for liveness questions — is all supplied, leaving no gap for a two-parameter read tool.

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 both core_id and space_id are already documented at the field level, including 'exact ID from swarm_list_cores; no fallback'. The description reinforces the provenance of core_id but adds no format or edge-case detail for space_id beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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?

The description names a specific verb and resource — inspect saved setup and heartbeat evidence for a device or Cloud Core — and scopes the input to IDs obtained from swarm_list_cores. It is clearly distinguishable from the sibling swarm_get_core (which fetches the runtime itself) and from swarm_list_agent_participants, which it explicitly hands off to.

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?

It states the trigger condition ('use before targeting that runtime'), a warning about interpretation ('read timestamps rather than assuming it is currently online'), and the exact alternative for a related question ('use swarm_list_agent_participants for connected-agent eligibility'). Both when-to-use and where-to-go-instead are explicit.

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