Skip to main content
Glama
Sign In

The White Report

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

Latest Telemetry (Machine Format)

telemetry_latest
Read-onlyIdempotent

Machine format (wr.telemetry.v1, testnet): the latest sealed compile envelope per telemetry metric; optional metric filter. Use telemetry_series instead for every envelope of one metric over time.

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": "telemetry_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricNoMetric id, as enumerated by this tool when metric is omitted; omit for the latest envelope of every metric.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / metric / description
      Previous value: -"Metric id; omit for all metrics."New value: +"Metric id, as enumerated by this tool when metric is omitted; omit for the latest envelope of every metric."
  2. Added

TDQS

A4.2/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 real context beyond that: the wire format/version (wr.telemetry.v1), the testnet environment, and that envelopes are 'sealed' (final). It stops short of describing the envelope payload, but it meaningfully enriches the annotation picture.

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 tight clauses: format/scope first, sibling routing second. Nothing redundant, and the most decision-relevant information (what it returns and how it differs from telemetry_series) 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?

With no output schema, the description provides the format identifier and environment, plus complete param guidance via the schema and full annotations. The only gap is that it doesn't sketch the envelope's return shape, a minor omission for a single-optional-param read tool.

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 100%, and the schema already explains that the metric id is enumerated by the tool and that omission returns all metrics. The description restates 'optional metric filter' without adding syntax or format detail, so the baseline 3 is appropriate.

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 resource ('latest sealed compile envelope per telemetry metric') plus an optional filter, and explicitly contrasts with sibling telemetry_series. The agent can distinguish it from telemetry_series 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 Guidelines4/5

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

Explicitly routes the agent to telemetry_series when the need is 'every envelope of one metric over time', which clearly bounds when this tool applies. No further exclusions or prerequisites are given, but the alternative condition is unambiguous.

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