Skip to main content
Glama

Follow a run

get_live_run
Read-onlyIdempotent

The run in progress, if any: how many answers are done of how many, each model's cells as they settle, and outcome counts; plus the poll's status, when it next runs, and the last run that settled. Poll this every few seconds while a run is active; when last_settled changes, read get_results. (GET /api/v1/polls/{id}/status)

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": {
      "id": "<id>"
    },
    "name": "get_live_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe poll's id, or its public address (slug).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered; the description adds genuinely new behavior in the form of the recommended polling interval and the change-detection signal (last_settled). It stops short of stating rate limits, backoff behavior, or what happens when no run is in progress beyond "if any", keeping it at a strong 4.

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?

A single dense, front-loaded sentence that spends no words on preamble, and the payload enumeration comes first with the usage instruction second. The semicolon-chained clauses make it slightly heavy to parse, but nothing is redundant.

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 burden of describing return content, and it does so at a useful level of detail (progress counts, per-model cells, outcome counts, poll status, next run). Ambiguities remain, such as the shape of "cells" and what is returned when no run exists, but the essential picture is complete for a polling read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Wait—reconsider: schema coverage is 100% with a single required parameter whose description already explains it accepts a poll id or public slug. The description adds only that the id refers to "the poll", duplicating the schema rather than extending it, so the 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?

The description names the specific resource (the run in progress for a poll) and enumerates its payload: answers done of total, per-model cells as they settle, outcome counts, poll status, next run time, and the last settled run. This is clearly separable from get_results and list_runs, and the parenthetical endpoint anchors it further.

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?

It gives an explicit cadence ("poll this every few seconds while a run is active") and a concrete handoff condition ("when last_settled changes, read get_results"), which names the sibling and the trigger for switching to it. When-not-to-use is implied by the active-run condition.

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.