Skip to main content
Glama
Sign In

The White Report

by io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC
OverviewDiscussionsAdmin

Telemetry Series (Machine Format)

telemetry_series
Read-onlyIdempotent

Machine format (wr.telemetry.v1, testnet): every sealed compile envelope for one metric id, oldest first. Use telemetry_latest instead when you only need the newest envelope per metric.

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": {
      "metric": "<metric>"
    },
    "name": "telemetry_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricYesMetric id, as enumerated by telemetry_latest (call it with metric omitted to list all metric ids).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / metric / description
      Previous value: -"Metric id."New value: +"Metric id, as enumerated by telemetry_latest (call it with metric omitted to list all metric ids)."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: results are ordered oldest first, the payload is a pinned machine format (wr.telemetry.v1), and this is testnet data. It does not say how large a series can get or whether results are truncated/paginated, which matters for a full-history listing.

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?

Two sentences, zero waste. The format/scope framing comes first and the sibling-routing rule closes it, so the decision-relevant content is front-loaded.

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?

For a one-required-param read tool with rich annotations and no output schema, the description covers ordering and format version adequately. The one remaining gap is that 'sealed compile envelope' is left as unexplained domain vocabulary, so an agent has no sense of the returned fields or volume.

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 parameter's schema text already explains how to obtain valid metric ids via telemetry_latest. The description adds only the 'one metric id' scoping restatement, so the schema does the heavy lifting and a baseline 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?

States a specific verb+resource: every sealed compile envelope for one metric id, in order, in the wr.telemetry.v1 machine format. It also names the sibling telemetry_latest and the axis on which the two differ (full series vs newest only), so an agent can pick correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the alternative and the selecting condition: use telemetry_latest when only the newest envelope per metric is needed. That is a clear when-to-use / when-not-to-use pair.

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

All The White Report toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources