Skip to main content
Glama
Sign In
@quikrun/mcp

@quikrun/mcp

by exit150
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_snippet

Retrieve a snippet's metadata and full source code by slug. Access complete snippet information for editing, running, or deployment.

Instructions

Get one snippet's metadata and full source code by slug.

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": "get_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe snippet slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. The verb 'Get' implies a read-only operation, and the description adds specifics about the return content ('metadata and full source code'). This is sufficient for a simple read tool, though it does not mention error conditions or explicit side-effect freedom.

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 sentence of 9 words, front-loaded with the action and object. Every word earns its place, with no redundant or filler content.

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?

Given its simplicity (one parameter, no output schema), the description is largely complete. It states what the tool returns (metadata and full source code). However, it could be improved by noting behavior on missing slugs, but this is not critical for a basic get operation.

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% for the single parameter 'slug', and the schema already describes it as 'The snippet slug'. The description only reinforces that the slug is the identifier. It adds no extra meaning beyond the schema, so the baseline score of 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 action ('Get'), the resource ('one snippet's metadata and full source code'), and the input ('by slug'). This effectively distinguishes it from sibling tools like list_snippets (which returns multiple snippets) or update_snippet (which modifies).

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 provides clear context that this tool is for retrieving a single snippet when the slug is known. It does not explicitly mention alternatives, but the phrase 'one snippet' implicitly differentiates from list_snippets. No exclusionary guidance is provided, but the usage scenario is clear.

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