Skip to main content
Glama
Sign In

pipehero

by io.github.pipehero
OverviewDiscussionsAdmin

list_api_runs

Read-only

Recent runs of an endpoint (newest first, default 5): who/what was sent and what came back. Use to see what happened the last time it was run.

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": {
      "collection_id": "<collection_id>"
    },
    "name": "list_api_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoRoute path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.
limitNoHow many runs to return, 1 to 20 (default 5).
methodNoHTTP method of the route, e.g. POST. Use with path instead of endpoint_id.
endpoint_idNoId of the endpoint. Alternative to method + path.
collection_idYesId from list_api_collections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"1 to 20."New value: +"How many runs to return, 1 to 20 (default 5)."
  2. Added

TDQS

A3.6/5.0
Behavior4/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 safety is covered. The description adds real value beyond that: result ordering (newest first), the default page size, and a sketch of the returned content ('who/what was sent and what came back') — important since there is no output schema.

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?

Two short sentences, front-loaded with the resource and its ordering/limit, followed by a use cue. No wasted text, though the second sentence is close to redundant with the first.

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 five parameters and no output schema, the description should say more about what a 'run' record contains and how results are selected (endpoint_id vs method+path). The schema fully covers inputs and the safety profile is in annotations, so it is adequate but not complete.

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%, so every parameter including the method+path vs endpoint_id alternative is already documented. The description only restates the default limit and ordering, adding little semantics beyond the schema — 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?

Names a specific verb+resource ('recent runs of an endpoint') and states scope (newest first, default 5) plus what the runs contain ('who/what was sent and what came back'). It is clearly distinct from sibling request-oriented tools like list_requests or get_request, though it never names an alternative explicitly.

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?

'Use to see what happened the last time it was run' gives an implied context of use, but there is no guidance on when to prefer this over list_requests, get_request, or replay_request, and no prerequisites (e.g., needing a collection_id first).

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

All pipehero toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources