Moltline Educator Toolkit

This connector has been deprecated

Superseded listing, not a dead server. This entry was imported from an early Glama registration under com.moltlinestudio.mcp; the same server is listed under its official MCP Registry name — use com.moltlinestudio/educator. Endpoint unchanged: https://mcp.moltlinestudio.com/educator — still live, still free on the free tier. Only this duplicate entry is deprecated.

Get Full Skill

get_full_skill

Read-onlyIdempotent

Load one paid skill's complete instructions from a product. PREMIUM (license).

Typical input {"slug": "curriculum-architect-hs", "skill_name": "unit-planner"} returns {"slug": ..., "skill": ..., "instructions": ""}.

Returns one named skill, selected by skill_name. Use when the caller wants one specific paid skill. Not for the free gateway skill, which get_free_skill returns with no plan, and not for every skill at once (get_full_product). 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "skill_name": "<skill_name>"
    },
    "name": "get_full_skill"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Product slug exactly as returned by list_products, e.g. "curriculum-architect-hs"; must be non-empty.
`skill_name`	Yes	Exact skill name as listed in that product's "skills" array from list_products, e.g. "unit-planner"; must be non-empty.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds real value: the PREMIUM/license gating requirement, and a non-obvious error contract (no protocol errors, returns {"error": ...} with a fix hint, safe to retry after correction). It does redundantly restate read-only/idempotent and leaves 'PREMIUM (license)' undefined, so it stops short of a 5.

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?

Front-loaded with purpose, then example, then selection rule, then exclusions and error behavior — a sensible ordering. The inline JSON example of input and output is somewhat verbose given the schema and output schema already encode both shapes.

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?

An output schema exists, so return values need no prose, and the description nonetheless covers selection, exclusions, license gating and error recovery. Nothing an agent needs to invoke this two-param read tool correctly 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 both params already carry examples, so the baseline is 3. The description adds the relationship between the two params (one skill selected by skill_name within a product slug) and a worked input/output pair, which clarifies selection semantics slightly beyond the schema.

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?

States a specific verb and resource ('Load one paid skill's complete instructions from a product') and explicitly bounds scope to a single named skill. It names both siblings it is not (get_free_skill, get_full_product), so an agent can select it without opening any schema.

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?

Gives an explicit positive trigger ('Use when the caller wants one specific paid skill') plus two explicit exclusions with the tool to use instead for each case. This is textbook when/when-not/alternatives guidance.

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

All Moltline Educator Toolkit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?