Skip to main content
Glama

get_session_stats

Retrieve current orchestration session statistics, including success rate, average completion time, worker counts, and attempt data, to monitor swarm performance.

Instructions

Get statistics about the current orchestration session including success rate, average completion time, worker counts, and attempt statistics.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "get_session_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: 'compact' for minimal output (no emoji/decorators), 'pretty' for full formatting (default)
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'Get' implies a safe read and the metric list adds real content beyond the name. However, it says nothing about error behavior when no session exists, whether output is scoped to the projectDir session, or whether the stat computation is expensive, which matters for a 30-plus-tool orchestration server.

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?

A single front-loaded sentence with zero filler, and the enumerated metrics are the useful part rather than padding. Nothing could be removed without losing information.

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

Completeness3/5

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

There is no output schema, so the description is the only source on return values, and it at least names the four stat categories. It is still thin for a reporting tool: no indication of return shape, whether values are counts versus percentages, or session-precondition failure.

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 description coverage is 100%, so projectDir (absolute path) and the format enum are already fully documented in the schema. The description adds no meaning beyond that, but the baseline of 3 applies since the schema does the work.

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 ('Get statistics about the current orchestration session') and enumerates the metrics returned (success rate, average completion time, worker counts, attempt statistics). It does not distinguish itself from sibling read tools like get_progress_log, get_audit_log, or check_all_workers, so an agent still has to infer which aggregate view it wants.

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 is given: nothing says whether this is a cheap snapshot to poll, whether it requires an active session, or when to prefer it over the other session/status siblings. The phrase 'current orchestration session' is the only contextual hint, and it is implied rather than stated.

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