Skip to main content
Glama

Get a starter project

get_starter

Returns a short-lived download link for a design's runnable Next.js starter project, stamped for the connected account, with the steps to run it. The link lasts ten minutes and can be opened more than once in that time. Up to 5 starters a day. Free designs need a connected account; paid designs need a plan as well.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe design's slug, from search_designs.

Output Schema

NameRequiredDescriptionDefault
fileYes
slugYes
stackYes
stepsYes
fileCountYes
startersLeftTodayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: the link lasts ten minutes, can be opened more than once, is stamped for the connected account, and is rate-limited to five per day. These details are exactly the operational context an agent needs before invoking the 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 front-loaded with the core purpose and then adds only useful operational details: link lifetime, reuse, rate limit, and account requirements. Every sentence carries relevant information and there is no redundancy.

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 tool has one fully documented parameter, an output schema, and clear annotations, the description completes the picture by covering authorization, rate limits, and link behavior. Nothing an agent needs in order to call it correctly appears to be missing.

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% and the single required parameter, slug, is fully documented in the schema as coming from search_designs. The description implies that the slug identifies the design but adds no semantic detail beyond the schema, so 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 states a specific verb and resource: it returns a short-lived download link for a design's runnable Next.js starter project. The scope is precise enough to distinguish it from get_design or search_designs, even without naming an alternative.

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 clearly explains eligibility and constraints: free designs need a connected account, paid designs need a plan as well, and the limit is five starters per day. It does not explicitly say when to use this versus sibling tools such as get_design, so it stops short of full alternative guidance.

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.