Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Get approval request

swarm_get_approval_request
Read-onlyIdempotent

Read an approval's action, resource and decision using an ID from swarm_list_approval_requests. Cannot decide or bypass the gate.

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": {
      "request_id": "<request_id>"
    },
    "name": "swarm_get_approval_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesApproval ID from swarm_list_approval_requests.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_id / description
      Previous value: -"Approval request ID returned by swarm_list_approval_requests."New value: +"Approval ID from swarm_list_approval_requests."
  2. Changed1 schema field changed
    • addedInput schema / properties / request_id / description
      Added value: +"Approval request ID returned by swarm_list_approval_requests."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is covered. The description still adds value by explicitly ruling out decision authority ('cannot decide or bypass the gate'), which an agent could otherwise assume from an approval-related tool, and by confirming what fields come back.

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?

Two short sentences, front-loaded with the read action and its return fields, then the negative constraint. No filler and nothing that repeats the annotation block verbatim.

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?

For a single-parameter read with a full output schema and rich annotations, the description covers purpose, ID provenance and the key non-capability. Only minor gaps remain, such as behavior on an unknown or expired request_id.

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 the single request_id parameter is fully documented, including its pattern and its origin in swarm_list_approval_requests. The description restates that same origin without adding format, validation or lookup-failure semantics, so it sits at the baseline.

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 ('Read') plus resource ('an approval') and enumerates the returned facets (action, resource, decision), which separates it cleanly from swarm_list_approval_requests and the other swarm_get_* siblings. An agent can pick it without opening the schema.

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?

Names the prerequisite sibling that produces the required ID ('using an ID from swarm_list_approval_requests'), which is the main routing decision here. It also excludes the mutation path by saying it 'cannot decide or bypass the gate', but never names the tool an agent should use instead when it actually needs to approve or deny.

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