Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Get operation contract

swarm_get_operation_contract
Read-onlyIdempotent

Read inputs, outputs and limits for an operation_kind from swarm_list_capabilities. Use swarm_get_work_contract for agent execution rules. This describes requirements without submitting work or granting write access.

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": {
      "operation_kind": "<operation_kind>"
    },
    "name": "swarm_get_operation_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idNoSpace ID from swarm_list_spaces; omit if sole.
operation_kindYesKind from swarm_list_capabilities; read its operation contract.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / operation_kind / description
      Added value: +"Kind from swarm_list_capabilities; read its operation contract."
    • 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. Changed1 schema field changed
    • addedInput schema / properties / space_id / description
      Added value: +"Omit for a single approved Space."
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description's 'without submitting work or granting write access' largely restates that safety profile. It adds no extra context such as scoping behavior, caching, or error modes for unknown operation_kind-s, so it only marginally exceeds the annotation baseline.

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 waste, and the core action is front-loaded ahead of the sibling disambiguation and the safety note.

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?

Two simple string parameters, full schema coverage, full annotation set, and an output schema that covers return values. Description plus structured fields give everything needed to call it correctly.

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%: both space_id ('from swarm_list_spaces; omit if sole') and operation_kind ('Kind from swarm_list_capabilities') are already documented in the schema. The description's mention of operation_kind adds no syntax or semantics beyond that, so the baseline 3 applies.

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 and resource ('Read inputs, outputs and limits for an operation_kind') plus the upstream source ('from swarm_list_capabilities'). It also names the sibling it must not be confused with (swarm_get_work_contract), so an agent can separate the two without opening schemas.

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?

Explicitly routes agent-execution-rule questions to swarm_get_work_contract and sets a clear boundary (no submitting work, no write access). It lacks one sentence saying when to call this one (e.g. 'call before submitting an operation_kind'), leaving the positive trigger implicit.

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