Skip to main content
Glama

Get starter kit

get_starter_kit
Read-onlyIdempotent

Call this when joining several fetched layouts into one deck file. Requests like "merge these into one file", "bundle it as a deck", or "make it one HTML" mean this tool. Returns the base CSS, assembly rules, spacing tokens, and a viewport snippet for standalone viewing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds only the payload contents, and does not clarify that calling it produces no deck file itself (the merge must be performed by the caller) — a meaningful behavioral distinction for a 'starter kit' 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?

Two sentences: the first front-loads the trigger conditions, the second enumerates the returned artifacts. The example phrasings are compact and each earns its place by improving routing accuracy; there is no filler.

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?

With no output schema, the description carries the burden of explaining return values and does so by listing the four artifact types. The remaining gap is not stating what the caller should do with the assembly rules or that merging happens outside this tool, which matters for a kit whose name implies action.

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 schema defines zero parameters, so the baseline is 4. The description is consistent with a no-argument retrieval tool and adds no misleading parameter expectations, though it could note that the target layouts are not passed in.

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 second sentence names concrete artifacts returned: base CSS, assembly rules, spacing tokens, and a viewport snippet, which makes the resource concrete rather than tautological. It does not explicitly say it retrieves a kit rather than performing the merge itself, so an agent could misread it as an assembler, and it never names sibling tools it differs from.

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?

Strong invocation routing: explicit user phrasings ('merge these into one file', 'bundle it as a deck', 'make it one HTML') map directly to this tool, and the prerequisite context of 'joining several fetched layouts' implies it follows get_layout calls. It gives no when-not guidance or named alternatives such as export_pptx or render_slide.

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