Skip to main content
Glama

List Runs

sandbase_runs
Read-only

List recent model/API calls, or supply service_id to list runs of an Agent Service.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of recent runs to return (default 10, max 50).
modelNoFilter by model name (e.g. 'openai/gpt-4o').
offsetNo
service_idNoList runs of this Agent Service instead of model predictions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It contributes the 'recent' scoping notion and the dual-mode behavior, but says nothing about ordering, what a run record contains, or how offset interacts with the recent-first window — gaps that matter for a paging tool.

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 tight sentence with the primary listing behavior front-loaded and the conditional mode second. The 'model/API calls' slash phrasing is mildly ambiguous, but there is no filler text to remove.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four optional parameters, rich annotations, and no output schema, the definition covers the core selection decision adequately. It still leaves the agent guessing about result ordering, the meaning of offset, and the shape of a returned run, which a listing tool of this complexity should address.

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 75%, so most parameters are already documented, including limit and model. The description's mention of service_id largely restates the schema's own note ('List runs of this Agent Service instead of model predictions'), and the undocumented 'offset' parameter gets no clarification in the description.

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 (list) and resource (recent model/API calls or Agent Service runs), with the two operating modes spelled out. It implicitly separates itself from sandbase_run_get by being a listing rather than a single-run fetch, but never names a sibling to make that contrast explicit.

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?

The clause 'or supply service_id' does tell the agent how to switch into the Agent Service mode, which is useful conditional guidance. However, there is no statement about when to prefer this over sandbase_run_get or sandbase_inspect, and no mention of pagination workflows, so usage is implied rather than prescribed.

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.