Skip to main content
Glama

transparency_metrics

Retrieve a metrics bundle covering trace coverage, anomaly counts, MTTR, and ZK proof generation rate to power public Proof of Observability dashboards.

Instructions

Get the full transparency metrics bundle: trace coverage, anomaly counts, MTTR, ZK proof generation rate, etc. Powers the public "Proof of Observability" dashboard.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "transparency_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a read via "Get" and suggests aggregation across subsystems, but says nothing about freshness/caching, cost or rate limits, whether the bundle is expensive to compute, or how partial failures are reported. The trailing "etc." actively obscures what is actually bundled.

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?

Two tight sentences, front-loaded with the verb and resource, with the dashboard rationale in the trailing position. "etc." is the one weak element — it trades precision for brevity in a way that leaves the payload undefined.

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?

For a zero-parameter tool with no output schema, the description is only partly sufficient: it names four of the bundled metrics and then stops, so an agent cannot tell the full response shape or which subsystems are covered. Adding the complete field list or a note on refresh semantics would make it complete.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly signals that no scoping arguments (time range, workspace) are accepted, which is itself useful information.

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?

States a specific verb and resource ("Get the full transparency metrics bundle") and enumerates contents: trace coverage, anomaly counts, MTTR, ZK proof generation rate. That enumeration distinguishes it from atomic siblings like metrics_query, anomalies_active, and zk_stats, though it never names an alternative directly.

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?

Usage is only implied by "Powers the public 'Proof of Observability' dashboard" and by the word "bundle" – an agent can infer this is the aggregated summary rather than a specific query. There is no explicit when-to-use or when-to-prefer-a-narrower-sibling guidance (e.g., metrics_query for a single series).

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