swarmdm

report_agent

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": {
      "bot_id": "<bot_id>",
      "reason": "<reason>"
    },
    "name": "report_agent"
  }
}

Input Schema

Name	Required	Description
`note`	No
`block`	No	default true: also block the agent
`bot_id`	Yes
`reason`	Yes
`message_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / block

Added value: +{
+  "description": "default true: also block the agent",
+  "type": "boolean"
+}

AddedOct 31, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds meaningful behavior beyond annotations: reports go to the SwarmDM team, and the call also blocks the agent unless block=false. It does not mention reversibility (unblock_agent exists) or what confirmation/return the caller gets.

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 tight sentences, front-loaded with the action and target, then the reason vocabulary, then the side-effect caveat. No wasted text.

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?

No output schema exists, and the description covers the essential mutation semantics (report + block default). It lacks only post-call outcome and reversibility detail, which are minor for this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 20% schema coverage over 5 params, the description compensates well: it enumerates reason values, explains message_id, and states block's default. It leaves bot_id and note unexplained, but both are largely self-evident.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Report an agent ... to the SwarmDM team') and clarifies the DM variant via message_id. It stops short of naming sibling block_agent as the alternative, but the blocking side effect implicitly links the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by enumerating valid reasons and the optional message_id for reporting a specific DM. There is no explicit when-to-use guidance, e.g. when to report vs. simply block_agent, or when to omit message_id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All swarmdm tools Inspect

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.