Moltline Educator Toolkit

Get Full Product

get_full_product

Read-onlyIdempotent

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

Typical input {"slug": "curriculum-architect-hs"} 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.

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>"
    },
    "name": "get_full_product"
  }
}

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.

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?

Adds context annotations cannot express: the PREMIUM license requirement, and a concrete error contract (no protocol error is raised; returns {"error": ...} with fix guidance), plus retry-safety after correcting input. It repeats the read-only/idempotent claims already carried by annotations, which costs it a point, but the error and licensing disclosure is genuine added value.

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-loads the purpose and routing exclusions, which is the right ordering, but the sentence "Returns persona plus every skill for one product" restates the opening line almost verbatim, and the full example return object is largely redundant given a declared output schema.

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?

For a single-parameter read tool with annotations and an output schema, everything an agent needs is present: scope, alternatives, license gate, error behavior, and retry semantics. No gaps remain that would cause a mis-call.

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 slug property is already documented, so the baseline is 3; the description adds a concrete worked input ({"slug": "curriculum-architect-hs"}) and ties invalid slugs to the returned error shape, which reinforces expected format 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 product in full: its persona plus every paid skill") and immediately names what it is not for at the sibling level. The distinction from get_full_skill, get_free_skill and list_products is explicit, so an agent can choose without opening schemas.

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 a positive condition ("Use when the caller wants the whole product") and two explicit exclusions with the alternatives named: single skill goes to get_full_skill, free look goes to list_products/get_free_skill. That is the full when/when-not/alternative triad.

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.