Skip to main content
Glama

groups_ai_providers_delete_ai_provider

Delete an AI provider from a group by specifying its provider ID.

Instructions

Delete Ai Provider [DELETE /api/groups/ai-providers/providers/{provider_id}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_idYes
Behavior2/5

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

No annotations provided, and description only indicates deletion. Missing behavioral details like irreversibility, required permissions, or side effects.

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?

Very concise, but overly sparse. Lacks structure or additional context that could fit in the same space.

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?

For a simple delete, description should mention return type (e.g., success status) or caution about irreversibility. It is incomplete given no annotations or output schema.

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 does not explain the 'provider_id' parameter. No details on how to obtain or format the ID.

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

Purpose2/5

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

The description 'Delete Ai Provider' restates the tool name, providing minimal purpose. It does not differentiate from sibling tools like update, get, or create, which also mention 'Ai Provider'.

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 vs alternatives such as update or create. Lacks prerequisites or conditions like need for permissions or provider existence.

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/2fst4u/mealie-mcp'

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