Skip to main content
Glama
djwmarcx

Better Mealie MCP

Delete Groups Ai Providers Providers By Provider

delete_groups_ai_providers_providers_by_provider

Remove an AI provider from Mealie by specifying its provider ID. Use this to delete unused or incorrect AI provider configurations.

Instructions

Delete Ai Provider

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_idYes
accept-languageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.20.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Delete Ai Provider', which conveys the destructive nature, but does not mention irreversibility, permissions, cascading effects, or any other behavioral consequence.

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?

The description is exceptionally concise: a single three-word phrase with no filler or irrelevant detail. It is front-loaded and every word contributes to the core meaning.

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?

While the operation is simple, the description omits important context such as whether deletion is permanent, whether authorization or group context matters, and what the accept-language parameter is for. The presence of an output schema does not compensate for these missing behavioral and usage details.

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 should compensate by explaining parameters. It does not mention provider_id or accept-language at all. The provider_id purpose is inferable from the tool name and the singular resource, but accept-language remains completely undocumented.

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 clear action and resource: 'Delete Ai Provider'. This conveys the primary purpose without ambiguity, though it does not differentiate the group-scoped variant from the admin-scoped sibling tools.

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 guidance on when to use this tool versus the sibling admin/group provider deletion tools. The description only states what the tool does, not when it should be selected over alternatives.

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