Skip to main content
Glama
Sign In
Mealie MCP Server

Mealie MCP Server

by bitmonster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mealie_api_multipart_operation_request

Execute non-sensitive Mealie API multipart operations by operation ID. Provide fields, parameters, and file sources; confirm mutations to proceed.

Instructions

Execute a non-sensitive multipart Mealie operation by OpenAPI operation ID.

file_sources maps multipart field names to direct HTTP(S)/file URLs or local paths. Mutations require explicit confirmation and an enabled scope.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "mealie_api_multipart_operation_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
path_paramsNo
file_sourcesNo
operation_idYes
query_paramsNo
confirmed_by_userNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 disclosure burden. It discloses that operations are 'non-sensitive' and that mutations require explicit confirmation, adding useful behavioral context. However, it omits details on response format, error handling, and authentication requirements.

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 sentences, front-loaded purpose, and no redundant wording. It earns a 4 because it is concise but could benefit from clarifying the term 'non-sensitive' or adding a brief example.

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?

Given the tool is a generic multipart operation executor with no annotations, no output schema, and 0% schema description coverage, this description is insufficient. It does not explain how to discover operation IDs, what the response looks like, or what errors may occur, making it unsafe for an agent to invoke correctly.

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%, so the description must explain all parameters. It only clarifies 'file_sources' (maps field names to URLs/paths) and 'confirmed_by_user' (via mutation confirmation requirement). The remaining parameters (operation_id, fields, path_params, query_params) are left undefined.

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?

Description states it 'Execute a non-sensitive multipart Mealie operation by OpenAPI operation ID', which is a specific verb+resource scope. However, it does not distinguish from its sibling tool 'mealie_api_operation_request', which likely serves the same purpose for non-multipart operations.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. It implies usage for multipart operations and notes mutations require confirmation, but does not mention when not to use or provide alternative tool names.

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