Skip to main content
Glama

ck_outcome_tracker

Close the reinforcement-learning feedback loop by recording session outcomes and accessing agent performance leaderboards.

Instructions

Record session outcomes or retrieve agent performance leaderboards to close the reinforcement-learning feedback loop. Three modes: record persists a session outcome (write operation); get_session reads a specific outcome by session_id (read-only); get_leaderboard returns ranked agent performance (read-only). For record mode: pass session_id, outcome (success/partial/failure), agent_id, and task_type. For get_leaderboard: pass workspace_id and optional window (days) and limit. Call after task completion before ending the session so ck_route and ck_cost_optimizer have fresh performance data for future routing decisions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesOperation mode that determines the tool behavior and return shape.
limitNoMaximum number of results to return.
windowNo
outcomeNoResult classification of the operation.
agent_idNo
task_typeNo
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
workspace_idNoWorkspace identifier for cross-session scope.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
entriesNo
outcomesNo
recordedNo
Behavior4/5

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

Annotations indicate non-read-only, non-idempotent, non-destructive. Description clarifies record mode as write operation and get_session/get_leaderboard as read-only, adding context about feedback loop and data freshness beyond annotations.

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?

Description is well-structured with mode breakdown and usage timing. Could be slightly more concise, but every sentence adds value.

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 output schema exists, description covers modes, parameters, and recommended timing adequately. Provides sufficient context for agent to use tool correctly.

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 coverage is 63% with descriptions for 5 of 8 parameters. Description adds meaning to mode and partially covers window, agent_id, task_type. However, not all parameters are fully detailed in text.

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 records session outcomes or retrieves leaderboards, distinguishing three modes with specific verbs (record, retrieve). It differentiates from sibling tools by focusing on outcome tracking and performance feedback.

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?

Explicitly states when to call (after task completion, before ending session) and why (to provide fresh data for ck_route and ck_cost_optimizer). Does not explicitly say when not to use, but context is clear.

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/aryaminus/controlkeel'

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