Moltline Catalog — 138 Agent Skills & Personas

Preview Product

preview_product

Read-onlyIdempotent

Preview one product: metadata, persona teaser, and paid-skill teasers. FREE.

Typical input {"slug": "inbox-zero-assistant"} returns {"slug": ..., "name": ..., "tagline": ..., "persona_preview": ..., "skills": [{"name": ..., "preview": ...}], "free_skill": ..., "note": ...}.

Returns teasers only, never full text. Use to judge a product before committing. Not for the complete persona or skill bodies (get_full_persona, get_full_product), and not when the caller wants instructions they can act on now (get_free_skill). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "unknown slug ''"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Product slug exactly as returned by search_catalog or recommend_products, e.g. "inbox-zero-assistant".

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by stating it returns only teasers (never full text), and details the error handling behavior (no protocol error, returns error object). This goes beyond annotations without contradicting them.

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 concise and well-structured: purpose is front-loaded, followed by example, then exclusions, and error behavior. Every sentence adds essential information with 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's simplicity (single parameter, has output schema, rich annotations), the description is fully complete. It covers input format, output shape, limitations, error handling, retry safety, and when to use versus alternatives.

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 coverage is 100% with a clear description of the 'slug' parameter. The description repeats the source of the slug (search_catalog or recommend_products) and provides an example, but does not add new semantic constraints. Baseline 3 is appropriate since the schema already fully documents the parameter.

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 previews one product, providing metadata, persona teaser, and paid-skill teasers. It differentiates from sibling tools by explicitly stating what it does not provide (complete persona/skill bodies from get_full_persona and get_full_product) and what it does (teasers only).

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?

The description gives explicit usage guidance: use to judge a product before committing. It also states when not to use: for complete persona/skill bodies (directing to siblings) or when actionable instructions are needed (get_free_skill). It further advises that errors return an object with a fix suggestion, and that retrying is safe after correction.

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 tools Inspect

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

Need Help?