Skip to main content
Glama

Moltline Business Suite

by com.moltlinestudio.mcp

Get Full Product

get_full_product
Read-onlyIdempotent

Load one product in full: its persona plus every paid skill. PREMIUM (license).

Typical input {"slug": "smb-ops-desk"} returns {"slug": ..., "name": ..., "persona": "", "skills": [{"name": ..., "instructions": ...}, ...], "free_skill": {...}}.

Returns persona plus every skill for one product. Use when the caller wants the whole product. Not for a single skill (get_full_skill) and not for a free look, which list_products and get_free_skill provide with no plan. 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
NameRequiredDescriptionDefault
slugYesProduct slug exactly as returned by list_products, e.g. "smb-ops-desk"; must be non-empty.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description reinforces these and adds unique behavioral detail: error handling (returns error object instead of protocol error) and retry safety. Slightly 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.

Conciseness5/5

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

Every sentence serves a purpose: purpose definition, example, scope clarification, error handling, and safety note. Front-loaded with the core action. No unnecessary words.

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 an output schema exists, the description appropriately provides an example return shape and covers error behavior. Also mentions licensing (PREMIUM) and idempotency. No gaps for the tool's complexity.

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 description coverage is 100%, so baseline is 3. The description adds context beyond the schema: specifies that the slug comes from list_products and gives a concrete example. This improves usability.

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 product in full (persona plus every paid skill) and explicitly distinguishes it from siblings get_full_skill and get_free_skill. The verb 'load' and resource 'full product' are 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?

Explicit usage guidance: 'Use when the caller wants the whole product.' Directly contrasts with alternatives: 'Not for a single skill (get_full_skill) and not for a free look, which list_products and get_free_skill provide with no plan.' Names sibling tools.

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

All Moltline Business 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.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: four financial calculators (cash_runway, loan_payment, target_price, unit_economics) each solve a different numeric problem, and four product/skill accessors (list_products, get_free_skill, get_full_skill, get_full_product) serve different retrieval needs. There is no overlap or ambiguity between tools.

Naming Consistency4/5

Tool names follow two internally consistent patterns: financial calculators use noun phrases (cash_runway, loan_payment) while product/skill tools use verb_noun style (list_products, get_free_skill). This grouping into predictable conventions is mostly consistent, but the mixed patterns across the two categories are a minor deviation from a single uniform style.

Tool Count5/5

With 8 tools, the server is well-scoped. Each financial calculator and product accessor earns its place, and the count is neither too thin nor too heavy for the stated 'Business Suite' purpose.

Completeness5/5

The financial tools cover the core calculations (runway, loan payment, target price, unit economics including break-even), and the product tools provide a complete access path from listing products to retrieving free skills, full skills, and full product details. There are no obvious dead ends or missing operations within the server's declared domain.

Resources