Skip to main content
Glama

Get a skill's scripts

get_bundle
Read-only

A download link (valid 15 minutes) for a skill's scripts and templates as a zip. Only call it when the skill's instructions say to. Download with curl and unzip where the instructions say.

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_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses the 15-minute link expiry, the archive contents (scripts and templates, as a zip), and the expected follow-up mechanics (curl and unzip). It doesn't state what happens if the link expires or the slug is invalid, keeping it from a 5.

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?

Three short sentences, front-loaded with the return value, then the gating condition, then the operational mechanics. Nothing is redundant and no sentence could be cut without losing information.

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?

For a one-parameter tool with no output schema, the description covers what is returned, its lifetime, and how to use it. Only edge-case behavior (expired link, invalid slug) is missing, which is minor at this complexity level.

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?

The single required parameter 'slug' has 0% schema description coverage. The description implies it identifies the skill whose bundle is fetched but never states the format or that it must be an existing skill. That's partial compensation for the coverage gap, so a middle score.

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?

The description names the concrete resource (a skill's scripts and templates) and the output form (a zip download link), which is clearly distinct from get_skill's metadata-style sibling. It doesn't explicitly contrast itself with get_skill, so it falls just short of a 5.

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?

It gives an explicit gating condition: 'Only call it when the skill's instructions say to,' which effectively tells the agent when not to call it. It does not name an alternative tool for the metadata case, but the constraint is clear and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources