Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

delete_groups_ai_providers_providers_by_provider

Delete a specific AI provider by its unique identifier to remove it from your group settings.

Instructions

Delete Ai Provider

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_idYes
accept-languageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Delete' with no mention of consequences, reversibility, or required permissions. This is insufficient for a destructive operation.

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

Conciseness2/5

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

The description is extremely short (3 words), but it sacrifices necessary detail. It is not concise in a helpful way; it is under-specified and leaves critical gaps.

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 performs deletion and has no output schema details, the description should explain return values, side effects, or success indicators. The minimal description does not provide enough context for an agent to fully understand the tool's behavior.

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%, and the description provides no explanation of the parameters. It does not describe what 'provider_id' represents (e.g., UUID of the AI provider) or the purpose of 'accept-language'. The agent lacks essential context to populate these fields correctly.

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?

Description states it deletes an AI provider, which is a clear verb+resource. However, it does not differentiate from similar sibling tools like 'delete_admin_groups_by_group_ai_providers_providers_by_p' which also deletes AI providers, leading to ambiguity.

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 guidance on when to use this tool versus alternatives. There is a sibling tool for admin-level deletion, but no context on prerequisites, permissions, or scenarios where this tool is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/djwmarcx/better-mealie-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server