Skip to main content
Glama

A figure beside its previous sample

since_last
Read-onlyIdempotent

Use this to ask whether a figure moved, and by how much. One measured figure with the stored sample it moved from: current, prior, delta, delta_ratio, both timestamps, definition id, unit, and whether the move is material under the published thresholds. window: sweep (the previous stored sample, the default), 24h, 7d or 30d. No prior sample inside the window returns gap: true and no delta; nothing is interpolated. Accepts a metric key or a definition id.

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_id": "<metric_id>"
    },
    "name": "since_last"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoWhat to compare with: sweep (the previous stored sample, the default), or the sample 24h, 7d or 30d backsweep
metric_idYesMetric key (actors_l7_plus) or definition id (rank.l7plus.v1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / window / description
      Added value: +"What to compare with: sweep (the previous stored sample, the default), or the sample 24h, 7d or 30d back"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description goes well beyond that: it defines what happens with no prior sample (gap: true, no delta, nothing interpolated) and reports materiality under published thresholds. These are edge-case and output-shape behaviors an agent cannot infer from the annotations.

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?

The purpose is front-loaded in one sentence, followed by the return-field list and then the window and gap semantics. The field enumeration is dense but earns its place given there is no output schema. Minor redundancy with the schema's window description is the only waste.

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 carries the burden of describing return values and does so explicitly, including the gap case and the absence of interpolation. For a two-parameter comparison tool with annotations covering safety, nothing an agent needs to call it correctly is missing.

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 documents both metric_id forms and every window enum value with the sweep default. The description restates the window options and the key-or-id acceptance, adding little beyond what structured data provides, so the baseline 3 applies.

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?

The description states a specific verb and resource: retrieve one measured figure alongside the stored sample it moved from, with current, prior, delta, delta_ratio and timestamps. That makes the single-comparison scope unmistakable. It does not name a sibling (e.g. metric_history) to draw the boundary explicitly, which keeps it short of a 5.

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?

"Use this to ask whether a figure moved, and by how much" gives a clear triggering question, and the window enumeration clarifies the comparison modes available. There is no explicit when-not guidance or named alternative for full time-series history, so it stops at clear context without exclusions.

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.