Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Aggregate Reflexions Tool

aggregate_reflexions

Aggregates recent agent reflections to surface recurring improvement themes, missing context, and tool requests, ordered by busiest agent; optionally scope results to one agent.

Instructions

Theme recent reflexions per agent (Phase 9b).

Reads ``reflexion_log`` entries from the last ``days`` days (default 14)
and returns the top recurring 'could improve', 'missing context', and
'tool wishes' themes, ordered by busiest agent.

Pass ``agent_slug`` to limit the scope; leave blank for all agents.

Input Schema

NameRequiredDescriptionDefault
daysNo
agent_slugNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, but the description clearly states it reads 'reflexion_log' entries (non-destructive) and returns aggregated themes. It does not contradict any annotations. Slight lack of mention of potential side effects, but none expected.

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 relatively concise (3 sentences) and front-loaded with the core purpose. It could be slightly tighter but is clearly structured.

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?

Given an output schema exists, the description covers the input parameters, data source, time window, and output categories sufficiently. It does not need to detail return values.

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?

Schema description coverage is 0%, but the description adds meaning: 'days' is time window (default 14 days), 'agent_slug' scopes to one agent or all. This compensates for the missing schema descriptions.

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 uses a specific verb ('Theme') and resource ('recent reflexions per agent') with clear scope (Phase 9b). It distinguishes from siblings like 'consolidate_reflexions' by focusing on aggregation and thematic grouping.

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?

The description implies when to use (to get top themes from recent reflexion logs) but does not explicitly mention when not to use or suggest alternatives among the many sibling tools.

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

Deploy Server

Other Tools