Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

Update Groups Ai Providers Prompts By Prompt Name

update_groups_ai_providers_prompts_by_prompt_name

Append to or override a named AI provider prompt for a group, with global instructions limited to append mode.

Instructions

Append to or override a prompt. The group-wide instructions (global) can only be appended.

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": {
      "prompt_name": "<prompt_name>",
      "mode": "<mode>",
      "content": "<content>"
    },
    "name": "update_groups_ai_providers_prompts_by_prompt_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
contentYes
prompt_nameYes
accept-languageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.30.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the safety burden. It does disclose a genuine mutation trait beyond the schema: 'global' group-wide instructions can only be appended, never overridden. It omits required permissions/role, whether override destroys prior prompt text, and whether missing content constraints apply — real gaps for a mutation endpoint, though the 'global' restriction is valuable context.

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?

Two short sentences, front-loaded with the operative behaviour and followed by the one hard constraint. No filler or repetition of the tool name.

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

Completeness3/5

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

An output schema exists, so return values needn't be described. But for a 4-param mutation tool with zero schema descriptions and no annotations, the description covers only mode semantics and the 'global' rule — it leaves prompt identification, content limits, and permission requirements unaddressed.

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 0% across 4 params, so the description must compensate. It does explain the meaning of the mode enum (append vs override) and pins `global` as a special prompt_name value, but says nothing about `content` (20,000-char cap, whether it replaces or concatenates under override) or `accept-language`.

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?

States a specific verb and resource ('append to or override a prompt') and clarifies that the operation depends on a mode, which is more precise than the tool name alone. It does not distinguish itself from the near-identical admin sibling update_admin_groups_by_group_ai_providers_prompts_by_pro or from update_groups_ai_providers_settings.

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?

Usage is only implied: an agent infers it should call list_groups_ai_providers_prompts first to learn valid prompt names, and that append vs override is chosen via mode. There is no explicit when-to-use/when-not statement, and no guidance on why the group-scoped version exists versus the admin-scoped sibling.

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