Skip to main content
Glama
Sign In

pipehero

by io.github.pipehero
OverviewDiscussionsAdmin

set_long_requests

Idempotent

Opt a tunnel into a 120-second ingress timeout instead of the 30-second default — for tool calls that legitimately run long, e.g. an MCP server exposed through the tunnel. Persists on the tunnel; pass enabled: false to revert to the 30-second default.

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>",
      "enabled": "<enabled>"
    },
    "name": "set_long_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue for the 120-second timeout, false to go back to the 30-second default.
subdomainYesTunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / enabled / description
      Added value: +"true for the 120-second timeout, false to go back to the 30-second default."
    • addedInput schema / properties / subdomain / description
      Added value: +"Tunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark this as a non-destructive, idempotent write. The description adds value beyond them by disclosing persistence ('Persists on the tunnel') and the exact revert semantics of enabled: false, which the annotations cannot convey. It omits whether the change applies to in-flight requests or requires tunnel reconnection.

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, front-loaded with the primary effect, followed by the example and the revert instruction. No filler.

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?

Complete for a two-parameter toggle: what it does, why, persistence, and how to revert. The only gap is operational timing (immediate effect vs. next connection), which is minor but would help an agent reason about sequencing.

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 both parameters are already documented, including the true/false semantics of enabled. The description restates the enabled behavior but adds no syntax or format detail beyond the schema, so 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?

Names a specific verb+resource ('opt a tunnel into a 120-second ingress timeout') and states the exact effect versus the 30-second default. It is unmistakable against siblings like list_tunnels or set_ws_passthrough.

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

Usage Guidelines4/5

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

Gives a concrete use case ('tool calls that legitimately run long, e.g. an MCP server exposed through the tunnel') and the revert path via enabled: false. It does not explicitly state when not to use this versus the default 30-second behavior, but the intended context is clear.

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