Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

Delete Groups Ai Providers Prompts By Prompt Name

delete_groups_ai_providers_prompts_by_prompt_name

Reset an AI provider prompt to its default by prompt name, removing any custom override.

Instructions

Reset a prompt to the default

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>"
    },
    "name": "delete_groups_ai_providers_prompts_by_prompt_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
prompt_nameYes
accept-languageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.30.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the four-word premise. It does not say whether the custom prompt text is destroyed or merely hidden, whether the action is reversible, what happens if no custom prompt exists, or what the response contains – essential information for an operation whose very name says "delete".

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but at four words it is under-specified rather than concise. It is efficiently structured yet wastes the one opportunity it has to clarify the delete-versus-reset ambiguity.

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?

An output schema exists, so return values need not be described, but for a destructive-sounding, zero-annotation, zero-coverage mutation tool the description is far too thin. It leaves the core semantic question – is this a deletion or a restoration – unanswered.

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

Parameters1/5

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

Schema description coverage is 0% for both parameters. The description never explains that prompt_name identifies which group-scoped prompt is targeted, nor what accept-language does, so it adds no meaning beyond the raw schema.

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

Purpose3/5

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

"Reset a prompt to the default" gives a verb and an object, but the object is only "a prompt" – it omits the group/AI-provider scope encoded in the name, and never reconciles "reset" with the tool name's "delete". It also does not distinguish the operation from the sibling update_groups_ai_providers_prompts_by_prompt_name, which an agent could easily confuse with it.

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?

There is no when-to-use or when-not-to-use guidance, no mention of the update sibling as the alternative, and no prerequisites (admin rights, group context). An agent must infer from the name alone when resetting is preferable to updating.

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