Skip to main content
Glama

dashboard

Read-only

Monitor RLHF performance metrics including approval rates, gate statistics, prevention impact, and system health status for comprehensive oversight.

Instructions

Get full RLHF dashboard -- approval rate, gate stats, prevention impact, system health

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • This function generates the data object for the "dashboard" tool.
    function generateDashboard(feedbackDir, options = {}) {
      const analyticsWindow = resolveAnalyticsWindow(options.analyticsWindow || options);
      const feedbackLogPath = path.join(feedbackDir, 'feedback-log.jsonl');
      const diagnosticLogPath = path.join(feedbackDir, 'diagnostic-log.jsonl');
      const entries = readJSONL(feedbackLogPath);
      const diagnosticEntries = readJSONL(diagnosticLogPath);
      const billingSummary = options.billingSummary || getBillingSummary(analyticsWindow);
    
      const approval = computeApprovalStats(entries);
      const gateStats = computeGateStats();
      const prevention = computePreventionImpact(feedbackDir, gateStats);
      const trend = computeSessionTrend(entries, 10);
      const health = computeSystemHealth(feedbackDir, gateStats);
      const diagnostics = aggregateFailureDiagnostics([...entries, ...diagnosticEntries]);
      const secretGuard = computeSecretGuardStats(diagnosticEntries);
      const analytics = computeAnalyticsSummary(feedbackDir, {
        analyticsWindow,
        billingSummary,
      });
      const observability = computeObservabilityStats(diagnosticEntries, diagnostics, secretGuard, analytics.telemetry);
      const instrumentation = computeInstrumentationReadiness(analytics, billingSummary);
      const delegation = summarizeDelegation(feedbackDir);
      const readiness = generateAgentReadinessReport({ projectRoot: PROJECT_ROOT });
    
      return {
        operational: {
          source: options.billingSource || 'local',
          fallbackReason: options.billingFallbackReason || null,
          window: analytics.window || analyticsWindow,
        },
        approval,
        gateStats,
        prevention,
        trend,
        health,
        diagnostics,
        delegation,
        secretGuard,
        analytics,
        observability,
        instrumentation,
        readiness,
      };
    }
  • Tool handler for the "dashboard" tool.
    case 'dashboard':
      return toTextResult(generateDashboard(getFeedbackPaths().FEEDBACK_DIR));
Behavior3/5

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

Annotations indicate readOnlyHint=true, which the description aligns with by using 'Get' (implying a read operation). The description adds context about the dashboard's scope (RLHF metrics) and content types, but doesn't disclose behavioral traits like rate limits, authentication needs, or response format beyond what annotations provide.

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?

The description is a single, efficient sentence that front-loads the core action ('Get full RLHF dashboard') and lists key metrics concisely. Every word contributes to understanding the tool's purpose without waste.

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?

Given the tool's simplicity (0 parameters, read-only annotation, no output schema), the description is adequate but has gaps. It explains what metrics are returned but not the format or structure, and it lacks usage context. For a read-only tool with no parameters, this is minimally viable but not fully comprehensive.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it appropriately focuses on the tool's output scope without redundancy, earning a baseline score above 3 due to the zero-parameter context.

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?

The description clearly states the tool's purpose with specific verbs ('Get') and resources ('full RLHF dashboard'), including the types of metrics it returns (approval rate, gate stats, prevention impact, system health). It distinguishes from siblings by focusing on dashboard metrics rather than specific operations like 'gate_stats' or 'feedback_stats', though it doesn't explicitly differentiate them.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, timing, or comparisons to sibling tools like 'gate_stats' or 'feedback_stats' that might provide overlapping or more specific data.

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/IgorGanapolsky/mcp-memory-gateway'

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