Skip to main content
Glama

Moltline Catalog — 138 Agent Skills & Personas

by com.moltlinestudio.mcp

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.8/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds that the payload is large, error handling returns a structured error object with fix instructions, and that every call is read-only and idempotent. No contradiction with annotations.

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?

The description is somewhat long but each sentence serves a purpose. It is front-loaded with the main action and clearly separated into usage, return size, and error behavior. Could be slightly more concise, but still well-structured.

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 only one parameter, is read-only, idempotent, and has an output schema, the description covers all necessary aspects: purpose, prerequisite steps, payload size, error handling, and retry safety. It is fully complete.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by showing a typical input/output example and specifying the slug comes from 'list_kits', which provides context 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?

The description clearly states the tool loads 'a themed kit and every member product in full.' It uses a specific verb ('load') and resource ('kit and member products'), and distinguishes from siblings like 'get_full_product' and 'list_kits'.

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 instructs to use only after 'list_kits' confirms the slug, and warns against using for a single product by naming the alternative 'get_full_product'. This gives clear when-to-use and when-not-to-use guidance.

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

All Moltline Catalog — 138 Agent Skills & Personas 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.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: listing, searching, recommending, previewing, and fetching different levels of detail. However, get_full_skill and get_free_skill could be confused since both return skill instructions but differ in which skill they target and plan requirements.

Naming Consistency4/5

The naming is largely consistent with a verb_noun pattern (list_kits, preview_product, search_catalog, etc.). However, there are minor deviations: get_free_skill uses 'free' as a qualifier rather than a verb, and upgrade_info is noun-heavy instead of verb_noun.

Tool Count5/5

With 10 tools covering discovery (search/recommend/list), preview, and detail retrieval across products, skills, personas, and kits, the count is well-scoped for a catalog API. Each tool has a clear role, and there is no noticeable bloat or deficiency.

Completeness4/5

The tool surface covers the full discovery-to-detail pipeline: browse/search/recommend, preview, then drill into free skill, full product, persona, kit, or specific paid skill. An 'upgrade_info' helper fills a support gap. A minor gap is the lack of a tool to list all products or browse by category without a keyword query.

Resources