Skip to main content
Glama
Sign In
@quikrun/mcp

@quikrun/mcp

by exit150
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

list_snippets

List all your QuikRun snippets with key details like name, slug, language, visibility, endpoint, run count, and last run.

Instructions

List all of the user's QuikRun snippets with a compact summary (name, slug, language, visibility, endpoint, run count, last run).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_snippets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses that the tool returns a compact summary with specific fields and that it lists all snippets, indicating a read-only broad retrieval. It does not discuss pagination or rate limits, but for a list tool this is minimal; the behavior is well conveyed.

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, front-loaded sentence that lists the output fields succinctly without any wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the zero-parameter schema and lack of output schema, the description fully covers what the tool does and what the response contains. It is complete for a listing tool of this simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so the baseline for parameter semantics is 4. The description adds context about the output fields, but there are no parameter details to clarify; thus a 4 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 uses a specific verb 'List' and resource 'QuikRun snippets', clearly distinguishing it from sibling tools like get_snippet (single) and create/update/delete. It also details the output fields, making its 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 Guidelines3/5

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

The description implies usage for retrieving an overview of all snippets, but it does not explicitly state when to use this tool versus alternatives like get_snippet, nor does it mention any exclusions or prerequisites. However, the 'List all' phrasing provides clear context.

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