Skip to main content
Glama

meta_metrics

Read-onlyIdempotent

Report aggregate improvement metrics—proposal/adoption counts, acceptance rate, prediction error, gain per cost, total cost, and confirmation counts—to judge how well proposals predict and pay off.

Instructions

Report aggregate improvement metrics: proposal and adoption counts, acceptance rate, mean absolute prediction error, gain per cost unit, total experiment cost and confirmation measurement counts. Use it to judge how well proposals predict and pay off; use ledger_history for individual events. Read-only. Returns one JSON object.

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": {
      "config": "<config>"
    },
    "name": "meta_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesPath of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • addedInput schema / properties / config / description
      Added value: +"Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path."
  2. First observedv0.1.7

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the 'Read-only' sentence is mostly redundant but consistent. The description adds genuinely new context absent from the structured fields: the aggregate nature of the output and that the return is a single JSON object with the listed metric families.

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?

Three front-loaded sentences: purpose and metric list, usage routing, then return shape. The metric enumeration is long but earns its place by defining what 'metrics' means; 'Read-only' slightly duplicates the annotations.

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?

With no output schema, the description supplies the return content and shape; the sole parameter is fully covered by the schema; and annotations carry the safety profile. An agent has everything needed to select and call this 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 description coverage is 100% and the single `config` parameter is fully documented in the schema, including the absolute/relative path semantics and the --config restriction. The description adds no parameter meaning, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Report aggregate improvement metrics') and explicitly enumerates the metrics: proposal/adoption counts, acceptance rate, mean absolute prediction error, gain per cost unit, cost, and confirmation counts. That enumeration distinguishes it clearly from the event-level sibling ledger_history, which is named.

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?

It states the decision the tool supports ('judge how well proposals predict and pay off') and routes individual-event needs to ledger_history. There is no explicit when-not guidance beyond that single exclusion, but the intended usage context is clear.

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