Skip to main content
Glama
Sign In
@quikrun/mcp

@quikrun/mcp

by exit150
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

run_snippet

Execute a QuikRun snippet to get its output, HTTP response summary, and logs. Override method, path, body, or run ad-hoc code.

Instructions

Run a snippet and return its output, HTTP response summary, and logs. Optionally override the request method, path, body, and bodyType, or run ad-hoc code.

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": {
      "slug": "<slug>"
    },
    "name": "run_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body payload.
codeNoAd-hoc code to run instead of the saved draft.
pathNoRequest path passed to the snippet.
slugYesThe snippet slug.
methodNoHTTP method for the run, e.g. GET or POST.
bodyTypeNoHow to interpret the body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, placing the burden on the description. It discloses return values (output, HTTP response summary, logs) and override capabilities, which is helpful. However, it does not mention potential side effects, required permissions, or whether execution has implications beyond returning data, which is a notable gap for an execution tool.

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?

The description is a single concise sentence that front-loads the core purpose, then lists optional behaviors without redundancy. It is appropriately sized for the tool's complexity and leaves no unnecessary wording.

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?

The description specifies return values and optional parameters, which covers the key aspects of a run operation even without an output schema. It could explicitly mention side effects or clarify whether it runs a saved draft versus deployed code, but the current text is largely complete for basic usage.

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?

All six parameters have schema descriptions, so the schema already provides high coverage. The description adds the concept of 'overrides' for method, path, body, and bodyType, and links code to ad-hoc execution, but this is marginal enhancement rather than new semantic meaning. Baseline 3 is appropriate.

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?

The description clearly states the tool runs a snippet and returns output, HTTP response summary, and logs, which is a specific action that distinguishes it from sibling CRUD and deployment tools. The verb 'Run' is direct and the resource 'snippet' is identified, making the purpose unambiguous.

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?

The description implies usage for executing snippets with optional overrides and ad-hoc code, which clearly positions it as the execution tool among sibling CRUD and deployment operations. It does not explicitly contrast with get_snippet or other tools, but the context makes when to use it clear enough.

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