Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Recipe Import

recipe_import
Destructive

Installs a SKILL someone shared with you — pass the skill_token from their recipe_export (or a raw recipe manifest JSON). Saves it to this Mac so recipe_run can use it. Importing only stores the skill. If a skill with the same name already exists, the import is saved under a non-colliding name. Returns {name, imported}.

Input Schema

NameRequiredDescriptionDefault
skillNoA skill_token from recipe_export, or a raw recipe manifest JSON string.
confirmNoIgnored; kept for older clients.
skill_tokenNoAlias for `skill` — the exact field name recipe_export returns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to save the skill. Without it the call returns a preview and saves nothing."New value: +"Ignored; kept for older clients."
  2. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to save the skill. Without it the call returns a preview and saves nothing.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / skill_token
      Added value: +{
+  "description": "Alias for `skill` — the exact field name recipe_export returns.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "skill"
-]New value: +[]
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations flag destructiveHint=true, but the description qualifies the mutation: it only stores the skill, and a name collision is saved under a non-colliding name rather than overwriting. That is meaningful context beyond the annotations, though it never states whether an existing same-named skill can be replaced or how to remove an import.

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?

Four short sentences, front-loaded with the verb and resource, then provenance, then scoping caveat, then return shape. Nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by naming the return object {name, imported} and explaining collision renaming. Missing only edge-case behavior (invalid token, what 'imported' false means).

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 description coverage is 100%, so the baseline is 3. The description restates what the schema already says (skill_token from recipe_export or raw manifest JSON) but adds no detail on format, validation, or what makes a token invalid.

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?

Specific verb and resource ('Installs a SKILL someone shared with you'), plus explicit input provenance (skill_token from recipe_export) and downstream consumer (recipe_run). This clearly distinguishes it from recipe_install/recipe_save/recipe_run siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains that importing only stores the skill and that recipe_run is what actually uses it, which sets expectations about when to call this versus run. It does not explicitly contrast with the nearby recipe_install sibling, leaving one ambiguity.

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

All Local MCP toolsInspect
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