Skip to main content
Glama
Sign In

pipehero

by io.github.pipehero
OverviewDiscussionsAdmin

list_requests

Read-only

List recent webhooks/requests captured for a tunnel. Returns id, method, path, status and bodies.

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": {
      "subdomain": "<subdomain>"
    },
    "name": "list_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
subdomainYesTunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / subdomain / description
      Added value: +"Tunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app."
  2. 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 safety is covered. The description adds useful context beyond that by naming the returned fields (id, method, path, status, bodies), but says nothing about how far back 'recent' reaches, result limits, or ordering.

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

Conciseness5/5

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

Two sentences with zero filler: the action and scope come first, the return shape second. Nothing is repeated from the title or annotations.

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?

For a single-parameter, read-only listing tool with no output schema, the description covers purpose and the shape of returned records, which is the essential gap. It falls slightly short on result volume and time-window bounds, which an agent would need to interpret 'recent'.

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 description coverage is 100%, and the subdomain parameter is fully documented there with an example drawn from list_tunnels. The description adds no parameter-level meaning beyond the schema, so the baseline of 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 ('List recent webhooks/requests captured for a tunnel') and names the entity that scopes it. It does not explicitly contrast with the closely related 'get_request' sibling (single-request retrieval), which is the main ambiguity for an agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative (e.g., use get_request for a single request's details, list_tunnels to discover subdomains). The only routing hint, 'from list_tunnels', sits in the schema rather than the description.

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