Moltline Personal Suite

List Products

list_products

Read-onlyIdempotent

List every product in the Personal Suite line with its included skills. FREE.

Takes no arguments. Returns a list of 20 product objects, each {"slug": "inbox-assistant", "name": ..., "tagline": ..., "skills": ["Skill A", ...], "free_skill": "Gateway Skill Name"}. Use the returned slug values with get_free_skill, get_full_product, or get_full_skill.

Returns metadata only - no persona text and no skill instructions. Use when the caller wants to see what this server covers. Not for keyword search across the whole 138-product catalog, which the catalog server's search_catalog does, and not for instructions the caller can act on (get_free_skill). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""}. 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
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

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 valuable behavioral context: 'Returns metadata only - no persona text and no skill instructions,' 'it never raises a protocol error — it returns an error object,' and 'Every call is read-only and idempotent, so after correcting the input it is always safe to retry.' This significantly enhances transparency.

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 well-structured with a clear lead sentence, followed by input/output details, usage guidance, and error handling. While slightly verbose, every sentence adds value and the information is front-loaded.

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 simplicity of the tool (no parameters, output schema exists), the description covers all relevant aspects: purpose, input, output structure, return behavior, error handling, and usage guidelines. It is complete and leaves no ambiguity.

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 tool has zero parameters, and the description confirms this with 'Takes no arguments.' Schema coverage is 100%, so the description adds no further parameter details but is clear and accurate.

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 explicitly states 'List every product in the Personal Suite line with its included skills.' It also distinguishes from siblings by noting that it returns metadata only, not skill instructions, and that the returned slug values are used with other tools like get_free_skill, get_full_product, and get_full_skill.

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 clearly specifies when to use the tool ('when the caller wants to see what this server covers') and when not to ('Not for keyword search across the whole 138-product catalog... not for instructions the caller can act on'). It also provides an alternative: 'search_catalog' from the catalog server.

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

All Moltline Personal Suite 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.5/5.0

Disambiguation4/5

Each tool targets a distinct task: budget_split for income allocation, tip_split for bill splitting, savings_goal for target saving, etc. There is slight potential confusion between budget_split and tip_split as both involve splitting money, but their inputs and purposes (monthly income vs. a single bill) are clearly differentiated. No two tools have overlapping functionality.

Naming Consistency4/5

Tool names follow a consistent snake_case verb_noun pattern (budget_split, tip_split, savings_goal, list_products, get_free_skill, etc.). The only minor inconsistency is that two tools use 'split' (budget_split, tip_split), which is fine as they refer to different kinds of splitting. Overall, the naming is predictable and clear.

Tool Count5/5

With 9 tools, the count is perfectly scoped for a personal suite covering personal finance (budget_split, tip_split, savings_goal), product browsing (list_products, get_free_skill, get_full_product, get_full_skill), time utilities (countdown_days), and learning (spaced_repetition_plan). Each tool serves a clear purpose without bloat or triviality.

Completeness4/5

The tool set covers the advertised areas: personal finance budgeting, goal saving, bill splitting, product discovery, countdowns, and spaced repetition. A minor gap is the lack of an update or delete tool, but this is acceptable since the server is primarily read-only and informational. The product tools provide a reasonable lifecycle (list, get free, get full, get skill).

Resources

Need Help?