Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

Create Recipes Create Html Or Json Stream

create_recipes_create_html_or_json_stream

Parse raw HTML or schema.org Recipe JSON like a URL with SSE progress, or import complete Mealie export JSON with full structure rather than schema.org parsing.

Instructions

Takes in raw HTML or a https://schema.org/Recipe object as a JSON string and parses it like a URL, streaming progress via SSE.

A complete recipe exported from Mealie (the JSON from an export zip, or the recipe as returned by the API) is imported with its full structure instead of being parsed as schema.org.

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": {
      "data": "<data>"
    },
    "name": "create_recipes_create_html_or_json_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
dataYes
includeTagsNo
accept-languageNo
includeCategoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.20.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that output is streamed via SSE and that Mealie-export JSON is imported with full structure instead of being schema.org-parsed — real behavioral context beyond the schema. But it omits that this is a write/creation operation with side effects, what happens on parse failure, and the shape of the SSE events, which matters for a streaming mutation tool.

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?

Two tight sentences with the input contract front-loaded and the Mealie-export nuance second. The awkward line break inside a sentence is cosmetic; no filler content is present.

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

Completeness2/5

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

For a 5-parameter streaming creation tool with no annotations, no output schema, and 0% schema coverage, the description is too thin: it says nothing about the return stream format, the role of the three boolean/locale flags, or error behavior. An agent could pick the right tool but would likely misuse the optional parameters.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must compensate. It explains only `data` (raw HTML or schema.org Recipe JSON string); `url`, `includeTags`, `includeCategories`, and `accept-language` are left entirely undefined in both schema and description, leaving an agent to guess at their effect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action (parse raw HTML or a schema.org Recipe JSON string into a recipe) and names the streaming transport (SSE). It also distinguishes the Mealie-export case from schema.org parsing, though it never names the non-streaming sibling create_recipes_create_html_or_json that an agent must choose between.

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

Usage Guidelines3/5

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

Implicit guidance is present: use this when you already hold an HTML blob or a JSON string rather than a URL, and use it when streaming progress matters. However, there is no explicit statement of when to prefer create_recipes_create_html_or_json (non-stream) or create_recipes_create_url_stream, and no prerequisites or failure conditions are given.

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

Deploy Server

Other Tools