Skip to main content
Glama
patrickdaj

agent-activity

by patrickdaj

summarize_tool_calls

Summarize tool call outcomes, failures, and usage for a given session, returning per-tool counts and total token cost.

Instructions

Summarize a session's tool calls: per-tool outcomes, failures, usage.

session accepts a full session UUID, a unique UUID prefix, or "latest" (resolved including the current session, since summarizing "my own" live session is a valid use case here). Returns per-tool invocation counts broken down by outcome (ok / error / pending / in_progress), overall totals, a main/sidechain split (tool calls made by subagents are included and tagged, never blended in untagged), the list of failing calls (each labeled error or rejected for permission denials), and the session's total token/cost usage. If this session is currently live (the most recently active discovered session), its trailing pending calls are labeled in_progress instead of pending. If session is ambiguous or matches no session, returns a structured {"error": ...} dict instead of raising. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: read-only, handles live sessions, returns structured errors, splits main/sidechain, and labels pending vs in-progress. This is comprehensive.

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?

The description is detailed but every sentence adds value; it is front-loaded with the overall purpose. A slightly more concise phrasing could be used, but overall well-structured.

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?

Given no output schema or annotations, the description covers input, behavior, and output structure (including error handling). It is complete for an agent to understand and use the tool correctly.

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

Parameters5/5

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

The input schema has 0% coverage (no description for the session parameter), but the tool description provides extensive detail on the parameter's meaning and acceptable values, fully compensating.

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?

The description clearly states the tool summarizes a session's tool calls with per-tool outcomes, failures, usage. It distinguishes from siblings (list_recent_sessions, tail_agent_log) by its specific focus on summarizing tool calls.

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?

The description explains how to specify the session (full UUID, prefix, 'latest') and covers the live session case. However, it does not explicitly state when not to use this tool or compare with siblings for alternative usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/patrickdaj/agent-activity-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server