Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Get Evaluation

swarm_get_evaluation
Read-onlyIdempotent

Inspect an existing assessment's outcome and evidence. Find IDs with swarm_list_evaluations. This neither reassesses work nor resolves approval or launches follow-up Runs.

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": {
      "evaluation_id": "<evaluation_id>"
    },
    "name": "swarm_get_evaluation"
  }
}

Input Schema

NameRequiredDescriptionDefault
evaluation_idYesEvaluation ID from swarm_list_evaluations.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / evaluation_id / description
      Previous value: -"Evaluation ID from swarm_list_evaluations or swarm_submit_evaluation."New value: +"Evaluation ID from swarm_list_evaluations."
  2. Changed1 schema field changed
    • addedInput schema / properties / evaluation_id / description
      Added value: +"Evaluation ID from swarm_list_evaluations or swarm_submit_evaluation."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavioral boundaries by clarifying that inspection does not trigger reassessment, approval resolution, or new Runs. It does not discuss error conditions or authorization, but with annotations and an output schema, the remaining gap is minor.

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 purpose followed by the ID source and explicit non-goals. There is no redundant or filler text.

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 simple read-only inspection tool with a complete output schema and full parameter schema coverage, the description supplies the necessary purpose, ID discovery path, and exclusions. Nothing essential for correct invocation is missing.

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?

The single parameter has 100% schema description coverage and already explains that the evaluation_id comes from swarm_list_evaluations. The description repeats that ID source but adds no additional format, validation, or retrieval semantics beyond the schema. Baseline 3 is appropriate when the schema fully documents the parameter.

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 states a specific verb and resource: inspect an existing assessment's outcome and evidence. It also differentiates the tool's scope from adjacent actions by saying it neither reassesses work nor resolves approvals nor launches follow-up Runs. This is enough for an agent to identify the tool's role among the many sibling get_* tools.

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 tells the agent to obtain the required ID via swarm_list_evaluations, which is the direct prerequisite for this tool. The negative guidance explicitly excludes reassessment, approval resolution, and follow-up Run launching, making the boundary clear.

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