Skip to main content
Glama

Metric history

metric_history
Read-onlyIdempotent

Use this to chart a figure over time. The history of one measured metric from the ledger's archive (daily points, plus 5-minute points for the last 48 hours). Gaps are real gaps, never filled. An unknown key returns similar keys and the full list of archived keys.

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": {
      "key": "<key>"
    },
    "name": "metric_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesMetric key, e.g. actors_l7_plus or observed_pay_usd_total
rangeNoHow far back to go: 24h, 7d, 30d (the default) or 90d30d

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / range / description
      Added value: +"How far back to go: 24h, 7d, 30d (the default) or 90d"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so extra credit goes to the data semantics disclosed beyond them: resolution tiers, the fact that gaps are never filled, and the unknown-key response returning similar keys plus the full archived key list. Return ordering and point counts are not described, keeping it below 5.

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?

Three short sentences, front-loaded with the use case, then scope, then data-integrity and error behavior. No filler and no restatement of the tool name.

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 carries the return-value burden and does so: point granularity, no gap filling, and the unknown-key response are all covered. Minor omissions such as point ordering or payload size bounds are low-risk for a two-parameter read tool.

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?

Schema coverage is 100%, so 3 is the floor; the description earns above that by explaining what the resolution actually looks like (daily points plus 5-minute points for the last 48 hours), which the schema's range enum does not convey. The mapping between each range value and its point density is implied rather than spelled out.

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 and resource ('chart a figure over time', 'history of one measured metric from the ledger's archive') and pins down scope as a single metric key, which cleanly separates it from a catalog-style listing tool such as list_metrics.

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 frames the use case ('use this to chart a figure over time') and explains the discovery fallback when a key is wrong, which tells the agent it need not pre-resolve keys elsewhere. It stops short of naming an alternative tool or stating when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.