Skip to main content
Glama

Swarm activity

get_swarm_activity
Read-onlyIdempotent

What the agents have been doing — the inter-agent transcript.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_swarm_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description carries no burden on the safety side, yet it adds nothing beyond them — no ordering (newest-first?), no pagination or truncation behavior, no statement of what a 'transcript' entry contains or how far back it reaches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short clause with no filler or repetition. It is front-loaded and readable, though its brevity comes partly from describing the concept rather than the operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and an undescribed limit parameter, the description is the only place an agent could learn what the call returns and how results are bounded, and it supplies neither. For a discovery-style read tool this leaves an agent guessing about freshness, scope, and result shape.

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

Parameters2/5

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

One parameter (limit, default 20, max 100) with 0% schema description coverage; the schema constrains the number but never says what is being counted. The description does not compensate — it never mentions limiting, page size, or that results are a bounded window of activity.

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

Purpose3/5

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

The phrase 'the inter-agent transcript' names a recognizable resource and distinguishes it from the ad/planner/content siblings, but there is no verb ('returns'/'retrieves') and 'what the agents have been doing' stays abstract — it doesn't say whether this is one agent's log, a session transcript, or an org-wide feed.

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

Usage Guidelines2/5

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

No when-to-use guidance at all: nothing about when an agent should pull the transcript (debugging a planner run? verifying delegated work?) and no mention of any alternative view such as get_plan_and_usage or get_planner_stage. The reader must infer the purpose from the title.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources