Skip to main content
Glama
stormhop

Kurlo

by stormhop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Run a saved request

run_request

Send a saved HTTP or GraphQL request with its collection defaults, auth and scripts, returning status, headers, body, timings and test results.

Instructions

Send one saved HTTP or GraphQL request with its collection defaults, auth and scripts, and return the status, headers, body, timings and test results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesRequest id, path (Collection/Folder/Name) or name.
variablesNoVariable overrides for this call, as name to value. They win over the environment.
environmentNoEnvironment name. Defaults to the one the server was started with.
maxBodyBytesNoMost bytes of the response body to return (default 65536, max 1048576).
browserOriginNoSend the call the way a browser on this page origin would, for example https://app.example.com: browser headers, the CORS preflight when one is needed, and the CORS error a browser would raise. Omit it and a saved request uses its own browser settings, if any.
browserCredentialsNoWith browserOrigin, make it a credentialed request (fetch credentials: include), which a wildcard Access-Control-Allow-Origin does not satisfy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds that collection defaults, auth and scripts execute, which tells the agent the call can have real side effects beyond a plain read. It stops short of saying whether runs are recorded in history or how failures surface, but the execution semantics are meaningfully disclosed.

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?

A single front-loaded sentence covering action, inputs inherited, and returned data, with no filler. Every clause earns its place.

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 usefully enumerates what comes back, and the six parameters are fully documented in the schema. The remaining gap is routing guidance against send_request/run_collection and any note on side effects or history recording.

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%, including detailed notes on browserOrigin and browserCredentials, so the schema carries the parameter burden. The description adds no parameter-level detail beyond the general mention of defaults and auth; 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?

States a specific verb and resource ('Send one saved HTTP or GraphQL request') and enumerates the return payload (status, headers, body, timings, test results). The word 'one saved' implicitly separates it from run_collection and send_request, but no sibling is named 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?

Usage is only implied through the phrase 'saved request' -- an agent must infer that ad-hoc sends belong to send_request and bulk runs to run_collection. There is no explicit when-to-use, when-not-to-use, or prerequisite statement.

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

Deploy Server

Other Tools