Skip to main content
Glama

Moltline Studio

by com.moltlinestudio

Get Full Kit

get_full_kit
Read-onlyIdempotent

Load a themed kit and every member product in full. PREMIUM (paid plan).

Typical input {"slug": "founder-kit"} returns {"slug": ..., "name": ..., "products": [{"slug": ..., "name": ..., "persona": ..., "skills": [...]}, ...]}.

Returns every member product of one bundle in full, so the payload is large. Use only after list_kits has confirmed the kit slug. Not for a single product (get_full_product). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "unknown kit ''"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesKit slug exactly as returned by list_kits, e.g. "founder-kit".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds value by stating the payload is large, error handling returns JSON with fix instructions, and reinforces idempotency. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with front-loaded purpose. Each sentence adds value, though the example payload could be trimmed. Still efficient and clear.

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's simplicity (1 param, output schema exists, annotations rich), the description covers purpose, usage, constraints, error behavior, and idempotency. No gaps remain.

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

Parameters5/5

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

Schema coverage is 100% with one parameter. Description adds meaning by explaining the slug comes from list_kits, provides an example value, and gives a typical input. Goes beyond the schema description.

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?

Description clearly states 'Load a themed kit and every member product in full.' It distinguishes from siblings like 'get_full_product' (single product) and 'list_kits' (just lists kits). The verb+resource scope is specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says 'Use only after list_kits has confirmed the kit slug' and 'Not for a single product (get_full_product).' Provides clear when-to-use and when-not-to-use with an alternative named.

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

All Moltline Studio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation4/5

The tools are mostly distinct, but the four get_full_* tools (kit, persona, product, skill) share a similar naming pattern and could be confused. Descriptions clarify the different payloads, so an agent can select correctly with careful reading.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern (get_free_skill, list_kits, search_catalog, etc.). The verbs vary by action but the structure is uniform and predictable.

Tool Count5/5

10 tools cover catalog search, recommendation, preview, and tiered content retrieval. This is well-scoped for a product catalog server, neither too few nor too many.

Completeness4/5

The surface covers browsing, searching, recommending, previewing, and retrieving free/full content, plus upgrade info. Minor gap: per-product pricing is not available except for kits, so agents cannot quote individual product prices directly.

Resources