Skip to main content
Glama

Moltline Personal Suite

by com.moltlinestudio

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
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.8/5.0
Behavior5/5

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

Adds significant context beyond annotations: confirms read-only and idempotent nature (matching annotations), specifies that it returns metadata only (no persona or skill instructions), and explicitly describes error handling behavior (never raises protocol error, returns error object). This goes beyond what annotations provide.

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 several sentences long but every sentence adds value: purpose, input, output structure, use cases, exclusions, error handling. It is front-loaded with the primary purpose and free status. Slightly longer than strictly necessary, but highly informative.

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 zero parameters, strong annotations, and the presence of an output schema, the description covers everything an agent needs: what the tool returns, how to use the returned data, when to call it, and error behavior. It is fully complete for decision-making.

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 explicitly states 'Takes no arguments.' With no parameters to document, the baseline is 4, and the description handles it appropriately without needing to add param details.

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 verb 'list' and the resource 'every product in the Personal Suite line with its included skills'. It distinguishes from sibling tools like get_free_skill, get_full_product, and get_full_skill by noting that this tool returns only metadata and is for overview, not details or instructions.

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 states when to use ('Use when the caller wants to see what this server covers') and when not to use ('Not for keyword search... search_catalog' and 'not for instructions... get_free_skill'). Provides clear exclusions and alternative tool references.

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 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 target distinct purposes (budgeting, counting days, skills, finances, scheduling, bill splitting). However, budget_split and savings_goal both deal with personal finance and could be confused by an agent, though their descriptions clarify the difference. Also, get_free_skill, get_full_skill, and get_full_product are related but clearly distinguished by access level and scope.

Naming Consistency4/5

Tool names use a consistent snake_case verb_noun pattern (e.g., budget_split, countdown_days, savings_goal). The only minor deviation is that some verbs are adjectives (free, full) rather than actions, but the pattern is still predictable and readable.

Tool Count5/5

With 9 tools, the set is well-scoped for a personal finance and productivity assistant. Each tool addresses a distinct, useful function without overwhelming the agent or leaving trivial gaps.

Completeness4/5

The tool surface covers key personal tasks: budgeting, savings goals, event countdowns, spaced repetition, bill splitting, and product exploration. A minor gap is the lack of a tool for expense tracking or recurring bills, but the domain is well-covered for the stated purpose.

Resources