Skip to main content
Glama
Sign In

Moltline Studio

by com.moltlinestudio
OverviewDiscussionsAdmin

Get Full Kit

get_full_kit
Read-onlyIdempotent

Load a themed kit and every member product in full. PREMIUM (license).

Typical input {"slug": "founder-kit"} returns {"slug": ..., "name": ..., "products": [{"slug": ..., "name": ..., "persona": ..., "skills": [...]}, ...]}.

Returns every member product of one bundle in full, so the payload is large. Use only after list_kits has confirmed the kit slug. Not for a single product (get_full_product). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": ""} (for example {"error": "unknown kit ''"}). 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_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesKit slug exactly as returned by list_kits, e.g. "founder-kit".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new context: a PREMIUM license requirement, a warning that the payload is large, and a precise error contract (never a protocol error, instead an {"error": ...} object with remediation). It also states retry safety after correction, which is actionable behavior an agent cannot derive from the hints alone.

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?

Purpose and license flag are front-loaded, then the return shape, then usage constraints, then error semantics — a sensible order. It is somewhat long for one parameter, and the inline JSON example plus the error example add bulk, but each element is informative rather than filler.

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 an output schema, this covers everything an agent needs: discovery precondition, license gating, payload size expectation, sibling disambiguation, and the non-throwing error contract with retry guidance. Nothing material is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the slug property already documents "exactly as returned by list_kits, e.g. founder-kit", so the description's example input largely restates the schema. No additional meaning (format constraints, validation rules, normalization) is added beyond what structured data provides, making the baseline 3 appropriate.

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?

"Load a themed kit and every member product in full" gives a specific verb and resource with explicit scope (all member products, not a summary). It distinguishes itself from list_kits (slug discovery) and get_full_product (single product) by name, so an agent can route without opening either 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?

It states a precondition ("Use only after list_kits has confirmed the kit slug") and an explicit exclusion with the correct alternative ("Not for a single product (get_full_product)"). Both the when-to-use and when-not-to-use cases are covered without inference.

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

All Moltline Studio toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources