Moltline Outbound Engine

Get Free Skill

get_free_skill

Read-onlyIdempotent

Load a product's free gateway skill with its complete instructions. FREE.

Typical input {"slug": "linkedin-outreach"} returns {"slug": ..., "skill": "", "instructions": ""}.

Returns exactly one skill - the product's free gateway skill - chosen automatically from the slug, with no plan required. Use when the caller wants usable instructions immediately. Not for the product's other skills: those are named and need get_full_skill with a skill_name, which requires a paid plan. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "unknown slug ''. Use list_products."}). 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 list_products, e.g. "linkedin-outreach".

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint true and idempotentHint true. The description adds valuable behavioral context: returns exactly one skill chosen automatically, never raises protocol errors but returns an error object with fix instructions, and confirms it is always safe to retry after correcting input.

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 well-structured: purpose, example JSON, exclusivity and usage context, error behavior, and safety guarantee. Every sentence adds value without redundancy. Front-loaded with the core action.

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 a single required parameter, rich annotations, output schema present, and clear sibling context, the description covers all necessary aspects: input format, usage boundaries, error handling, and behavioral guarantees. Nothing is missing.

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% and the schema describes 'slug' as 'Product slug exactly as returned by list_products'. The description reinforces this with an example ('{

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 it loads 'a product's free gateway skill with its complete instructions', using a specific verb-resource pair. It distinguishes from the sibling tool 'get_full_skill' by noting the difference in skill selection and plan requirement.

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 guidance is provided: 'Use when the caller wants usable instructions immediately' and 'Not for the product's other skills: those are named and need get_full_skill with a skill_name, which requires a paid plan.' This makes the choice between siblings unambiguous.

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

All Moltline Outbound Engine 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.7/5.0

Disambiguation5/5

Each tool has a well-defined, unique purpose. The product/skill tools (list_products, get_free_skill, get_full_skill, get_full_product) are differentiated by scope and access level, and the writing tools (audit_copy, subject_line_scorer, sequence_planner, utm_builder) cover distinct aspects of outreach creation with no overlap. Descriptions explicitly state what each tool is not for, further reducing ambiguity.

Naming Consistency5/5

All tool names use snake_case with a consistent verb_noun pattern: 'verb_object' for actions like list_products, get_free_skill, and 'noun_verb' for compound tools like subject_line_scorer. There is no mixing of styles or inconsistent abbreviations.

Tool Count5/5

With 8 tools, the set is well-scoped for an outbound engine. It covers product discovery, skill retrieval, copy auditing, subject line scoring, sequence planning, and UTM building—neither too few to be useful nor too many to be overwhelming.

Completeness5/5

The tool surface appears complete for its stated domain: product/skill lookup, content quality checks (audit_copy, subject_line_scorer), cadence planning (sequence_planner), and campaign tracking (utm_builder). There are no obvious gaps for the knowledge and planning phase of outbound outreach.

Resources

Need Help?