Skip to main content
Glama
Sign In

LastPing

by dev.lastping
OverviewDiscussionsAdmin

List runs

list_runs
Read-onlyIdempotent

Requires the read scope or higher. Lists runs across every monitor in the project, newest started first, including runs that exist only as OpenTelemetry traces (traced: true). Each run carries check_id, check_name, rid, title, outcome, started_at, ended_at, duration_ms, step_count, exit_code, its incident, and when traced span_count, tokens, cost_usd and cost_source (client, estimated or mixed); plus agent_id, agent_name, source_name, multi_trace, project (the Claude Code session's folder), receiving_spans (spans in the last 2 minutes), in_hook_session, is_test (excluded from counts). failure_cause is 'upstream' when the run ended on the model provider's API error (pages after 3 in a row, or failure_threshold when higher; upstream_error names it) or 'assertion' when a success failed an output assertion or declared expectation. outcome: succeeded, failed, cancelled, blocked, running or unfinished (started, never ended within max_runtime_s or 24h; never pages). Filters combine and also narrow counts (per-outcome totals). Pages with next_cursor. untrusted_fields names the data fields LastPing did not write (job output, exporter data or user-supplied names).

Input Schema

NameRequiredDescriptionDefault
qNoOnly runs whose run id (rid) contains this text.
agentNoOnly runs of this agent (agent UUID or slug).
limitNoRuns per page (default 20, max 100).
modelNoOnly runs that called this model, by exact model id.
sinceNoRFC 3339 start of the window, e.g. 2026-09-01T00:00:00Z. Default 7 days ago; at most 90 days back.
untilNoRFC 3339 end of the window. Default now.
cursorNonext_cursor from the previous page, verbatim.
tracedNotrue: only runs that hold spans. Omitted or false: every run.
monitorNoOnly this monitor's runs (monitor UUID).
outcomeNoOnly runs with this outcome.
projectNoOnly runs whose Claude Code hook start carried this project label: the name of the folder that holds the git repository the session worked in, or the folder's name when it is not in a repository.
trace_idNoOnly the run a trace became: 8 to 32 hex digits of its trace id. Finds runs made from a trace with no run id, not runs that named their own.
has_errorNotrue: only runs with a span that reported an error. false: only runs without one.
operationNoOnly runs with a span whose name starts with this text.
dependencyNoOnly runs that called this dependency, by its exact name as get_agent_dependencies reports it (e.g. api.github.com).
min_cost_usdNoOnly runs whose cost is at least this many US dollars, as a decimal string, e.g. "0.25".
min_duration_msNoOnly runs that took at least this many milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project / description
      Previous value: -"Only runs whose Claude Code hook start carried this project label: the name of the folder the session worked in."New value: +"Only runs whose Claude Code hook start carried this project label: the name of the folder that holds the git repository the session worked in, or the folder's name when it is not in a repository."
  2. Changed1 schema field changed
    • changedInput schema / properties / traced / description
      Previous value: -"true: only runs that hold spans. Omit or false for every run."New value: +"true: only runs that hold spans. Omitted or false: every run."
  3. Changed2 schema fields changed
    • changedInput schema / properties / min_cost_usd / description
      Previous value: -"Only runs whose estimated cost is at least this many US dollars, as a decimal string, e.g. \"0.25\"."New value: +"Only runs whose cost is at least this many US dollars, as a decimal string, e.g. \"0.25\"."
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Only runs whose Claude Code hook start carried this project label: the name of the folder the session worked in.",
+  "type": "string"
+}
  4. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the auth scope required, result ordering, pagination via next_cursor, that filters also narrow per-outcome counts, the paging rule for upstream failures (3 in a row or failure_threshold), that 'unfinished' never pages, and the meaning of untrusted_fields. This is unusually rich behavioral context for a read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, which is good, but the middle is a run-on enumeration of ~25 return fields across several semicolon-chained clauses, and the outcome enum values repeat what the schema already declares. Dense and somewhat unstructured given the volume.

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 must carry return-value semantics, and it does: the run field set, traced-only fields, cost_source, failure_cause/upstream_error, outcome definitions and untrusted_fields. Combined with the schema's 17 fully documented filters, an agent has everything needed to call and interpret it.

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 the baseline is 3; the description earns above that by explaining cross-parameter behavior ('Filters combine and also narrow counts (per-outcome totals)') that no individual schema property states. It adds filter-interaction semantics rather than just echoing field names.

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 ('Lists runs across every monitor in the project') plus the ordering ('newest started first'), which is more than a restatement of the name. It doesn't explicitly distinguish itself from near-siblings like get_run or get_run_history, so the agent has to infer the selection boundary.

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?

Provides a prerequisite ('Requires the read scope or higher') but gives no explicit when-to-use versus alternatives such as get_run (single run) or get_run_history. Usage is implied by the tool name and the describe-the-filters scope, not stated.

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

All LastPing 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